You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manages a PCD cluster blueprint — the shared, declarative configuration that virtualized clusters inherit (networking, image library, VM storage, and Cinder backends). PCD supports a single blueprint per region, so the common workflow is to terraform import the existing blueprint and then manage it. Changing name forces a new resource. Destroying this resource only removes it from Terraform state — it does not delete the region's blueprint (use the PCD UI for that).
6
+
Manages a PCD cluster blueprint — the shared, declarative configuration that virtualized clusters inherit (networking, image library, VM storage, and Cinder backends). PCD supports a single blueprint per region, so the common workflow is to terraform import the existing blueprint and then manage it. Changing name forces a new resource. Destroying this resource deletes the blueprint from PCD, so destroy whatever depends on it first (a pcd_host_config referencing it through cluster_name, and the clusters and host roles built on it). To stop managing an imported blueprint without deleting it, remove it from state with terraform state rm instead.
7
7
---
8
8
9
9
# pcd_cluster_blueprint (Resource)
10
10
11
-
Manages a PCD cluster blueprint — the shared, declarative configuration that virtualized clusters inherit (networking, image library, VM storage, and Cinder backends). PCD supports a single blueprint per region, so the common workflow is to `terraform import` the existing blueprint and then manage it. Changing `name` forces a new resource. Destroying this resource only removes it from Terraform state — it does not delete the region's blueprint (use the PCD UI for that).
11
+
Manages a PCD cluster blueprint — the shared, declarative configuration that virtualized clusters inherit (networking, image library, VM storage, and Cinder backends). PCD supports a single blueprint per region, so the common workflow is to `terraform import` the existing blueprint and then manage it. Changing `name` forces a new resource. Destroying this resource deletes the blueprint from PCD, so destroy whatever depends on it first (a `pcd_host_config` referencing it through `cluster_name`, and the clusters and host roles built on it). To stop managing an imported blueprint without deleting it, remove it from state with `terraform state rm` instead.
MarkdownDescription: "Manages a PCD cluster blueprint — the shared, declarative configuration that virtualized "+
65
65
"clusters inherit (networking, image library, VM storage, and Cinder backends). PCD supports a single "+
66
66
"blueprint per region, so the common workflow is to `terraform import` the existing blueprint and then "+
67
-
"manage it. Changing `name` forces a new resource. Destroying this resource only removes it from "+
68
-
"Terraform state — it does not delete the region's blueprint (use the PCD UI for that).",
67
+
"manage it. Changing `name` forces a new resource. Destroying this resource deletes the blueprint from "+
68
+
"PCD, so destroy whatever depends on it first (a `pcd_host_config` referencing it through `cluster_name`, "+
69
+
"and the clusters and host roles built on it). To stop managing an imported blueprint without deleting "+
70
+
"it, remove it from state with `terraform state rm` instead.",
69
71
Attributes: map[string]schema.Attribute{
70
72
"name": schema.StringAttribute{Required: true, MarkdownDescription: "The blueprint (cluster) name. Changing this forces a new resource.", PlanModifiers: []planmodifier.String{stringplanmodifier.RequiresReplace()}},
71
73
// networking_type and enable_distributed_routing are not user-configurable
0 commit comments