Deployment Lifecycle Operations
Important Legacy Notice: Google Cloud Deployment Manager reached end of support on March 31, 2026. All new infrastructure deployments should be directed to Google Cloud Infrastructure Manager or Terraform. The following content is provided strictly as legacy reference for understanding, maintaining, or decommissioning existing deployments.
What you'll learn: How legacy Google Cloud Deployment Manager handled creation, previews, updates, and deletions, and how state was historically managed.
Understanding the Legacy Deployment Lifecycle
For organizations maintaining existing infrastructure, understanding how Deployment Manager tracked the state of resources is critical for safe maintenance and eventual migration. Deployment Manager functioned by ensuring cloud resources matched a declared YAML configuration through four main lifecycle phases.
Legacy Reference Operations
The following gcloud deployment-manager commands are provided as historical reference for maintaining existing setups or decommissioning deployments, and should not be run for new infrastructure.
Preview: Administrators tested what would happen without actually applying changes—a "dry run" that showed planned changes and caught configuration errors early.
# Legacy reference for previewing updates
gcloud deployment-manager deployments update my-deployment --config config.yaml --preview
Update: Used to modify an existing deployment. Deployment Manager calculated the difference between the modified YAML and the current infrastructure state, adjusting only what changed.
# Legacy reference for updating existing deployments
gcloud deployment-manager deployments update my-deployment --config config.yaml
Create: Historically launched a new deployment from a configuration file. Deployment Manager provisioned all defined resources and began tracking them.
# Legacy reference for creation
gcloud deployment-manager deployments create my-deployment --config config.yaml
Delete: Removes the deployment and (by default) all resources it created. This command remains highly relevant for tearing down and decommissioning legacy infrastructure.
# Reference for decommissioning legacy deployments
gcloud deployment-manager deployments delete my-deployment
State Management Matters
Legacy Deployment Manager maintained a state record of every deployment—tracking which resources existed, their properties, and their relationships. This state allowed the service to perform intelligent updates and prevent resource conflicts. When maintaining these legacy systems prior to migration, administrators had to avoid manually modifying resources in the console, ensuring updates went through the configuration file to keep state synchronized.
Key Takeaway: Google Cloud Deployment Manager reached end of support on March 31, 2026; its lifecycle operations (create, preview, update, and delete) now serve purely as legacy reference for safely maintaining or decommissioning existing infrastructure while new workloads utilize Terraform or Infrastructure Manager.