Merge pull request #33 from platform9/feat/blueprint-resource

feat(resmgr): pcd_cluster_blueprint resource (write path) — validated live

Author: PF9-pushkar

CHANGELOG.md

@@ -95,8 +95,13 @@ All notable changes to this project are documented here. The format is based on
   from the Keystone catalog, token via the shared ProviderClient) plus `pcd_host_config` (interface
   ↔ traffic-type mapping and physical-network labels), `pcd_host_role` (assign a role such as
   `pf9-ostackhost-neutron` to a host), `pcd_host_config_assignment` (attach a host config to a host),
-  and a `pcd_cluster_blueprint` data source (read a blueprint by name). The `pcd_cluster_blueprint`
-  resource (write path) is tracked separately — see DECISIONS.md.
+  and a `pcd_cluster_blueprint` data source (read a blueprint by name).
+- `pcd_cluster_blueprint` resource — manage a cluster blueprint (networking, image library, VM
+  storage, HA/rebalancing, and Cinder backends). PCD supports one blueprint per region, so the
+  usual workflow is to `terraform import` the existing blueprint and manage it in place (in-place
+  update verified live). The write API requires the whole object, so all attributes are
+  `Optional+Computed` and round-tripped; `storage_backends_json` is sensitive (driver credentials)
+  and is read back so writes preserve the current backends unless you change it.
 - Registry documentation generation wired via `tfplugindocs` (`make generate`) — renders
   `docs/` for every resource and data source plus the provider index from schema
   descriptions. Generated docs are produced on demand / at release and are not committed.

examples/resources/pcd_cluster_blueprint/import.sh

@@ -0,0 +1 @@
+terraform import pcd_cluster_blueprint.example <blueprint_name>

examples/resources/pcd_cluster_blueprint/resource.tf

@@ -0,0 +1,17 @@
+# PCD supports a single blueprint per region. The usual workflow is to import
+# the existing blueprint (see import.sh) and then manage it here.
+resource "pcd_cluster_blueprint" "example" {
+  name            = "cluster-1"
+  networking_type = "ovn"
+  dns_domain_name = "example.local."
+
+  virtual_networking = {
+    enabled       = true
+    underlay_type = "vlan"
+    vnid_range    = "1000:2000"
+  }
+
+  # storage_backends_json is omitted here so the imported Cinder backends are
+  # preserved. It is required only when creating a brand-new blueprint, and it
+  # carries driver credentials (sensitive).
+}

internal/provider/provider.go

@@ -91,6 +91,7 @@ func (p *pcdProvider) Resources(_ context.Context) []func() resource.Resource {
 		dns.NewRecordSetResource,
 		keymanager.NewSecretResource,
 		keymanager.NewContainerResource,
+		resmgr.NewBlueprintResource,
 		resmgr.NewHostConfigResource,
 		resmgr.NewHostRoleResource,
 		resmgr.NewHostConfigAssignmentResource,

internal/services/resmgr/blueprint_data_source.go

@@ -53,9 +53,21 @@ type blueprintAPI struct {
 	ImageLibrarySharedStorage bool                  `json:"imageLibrarySharedStorage"`
 	InstanceSharedStorage     bool                  `json:"instanceSharedStorage"`
 	VMStorage                 string                `json:"vmStorage"`
+	VMHighAvailability        *haAPI                `json:"vmHighAvailability"`
+	AutoResourceRebalancing   *rebalanceAPI         `json:"autoResourceRebalancing"`
 	StorageBackends           json.RawMessage       `json:"storageBackends"`
 }
 
+type haAPI struct {
+	Enabled bool `json:"enabled"`
+}
+
+type rebalanceAPI struct {
+	Enabled                  bool   `json:"enabled"`
+	RebalancingStrategy      string `json:"rebalancingStrategy"`
+	RebalancingFrequencyMins int64  `json:"rebalancingFrequencyMins"`
+}
+
 type virtualNetworkingAPI struct {
 	Enabled      bool   `json:"enabled"`
 	UnderlayType string `json:"underlayType"`