@@ -103,6 +103,28 @@ Both PENDING items are lab-side configuration gaps (Platform9 / lab-ops), not pr
103103defects; their acceptance tests flip green on a properly-configured PCD cloud.
104104
105105
106+ ## 2026-07-13 — api-docs coverage: PCD-native services (resmgr / cluster blueprint)
107+
108+ An audit of ` docs.platform9.com/api-docs ` (7 services) vs the provider found the
109+ OpenStack-service families fully/near-covered, but two PCD-native services entirely
110+ unbuilt: ** cluster-blueprint** (` resmgr/v2 ` ) and ** kubernetes** (PCD-K/CAPI). Tier-2
111+ gaps (blockstorage volume_type/snapshot/backup, identity group) were closed first
112+ (#26 , #27 ).
113+
114+ For the cluster-blueprint family, ` resmgr ` is the first ** non-OpenStack** service, so it
115+ gets a hand-written REST client (` Config.ResmgrV2Client() ` ) that resolves the ` resmgr `
116+ catalog endpoint and reuses the authenticated ProviderClient for tokens (verified live
117+ against the CE lab). Shipped: ` pcd_host_config ` , ` pcd_host_role ` ,
118+ ` pcd_host_config_assignment ` , and a ` pcd_cluster_blueprint ` ** data source** .
119+
120+ ** The ` pcd_cluster_blueprint ` resource (write path) is deliberately deferred to a focused
121+ follow-up.** Its object is uniquely hairy: a full-object ` PUT ` (partial models risk
122+ clearing fields), a ` storageBackends ` map that carries ** plaintext driver credentials** ,
123+ and create semantics (` POST ` vs ` PUT ` ) that cannot be safely verified without mutating the
124+ lab's single working blueprint. It deserves its own careful pass. The mutating resmgr
125+ resources' acceptance tests are opt-in (` PCD_ACC_RESMGR ` ) so they never touch a live
126+ cluster by accident.
127+
106128## 2026-07-12 — backed out code PCD does not ship (VPNaaS, Octavia L7)
107129
108130Live inspection of the CE lab's service catalog (all 14 services + the Octavia provider
0 commit comments