Deployment Outputs
Important Notice: Google Cloud Deployment Manager reached end of support on March 31, 2026. The following content is provided strictly as legacy reference for maintaining or migrating existing deployments. For all new infrastructure work, direct your efforts to Google Cloud Infrastructure Manager or Terraform.
What you'll learn: How deployment outputs were defined and exposed to make important infrastructure values accessible in legacy Google Cloud Deployment Manager configurations.
Why Deployment Outputs Matter
When Deployment Manager created infrastructure, it generated many values that administrators needed later—such as IP addresses, database connection strings, and generated resource names. Deployment outputs allowed engineers to explicitly publish these values so they were easy to retrieve without digging through deep resource details.
Think of outputs like a restaurant's receipt: instead of asking the kitchen to remember what you ordered, you got a clear summary of exactly what was provisioned.
Defining Outputs in Legacy Configurations
When reviewing existing YAML configuration files, you will often find an outputs section at the top level (alongside resources). Each output requires a name and a value, typically referencing deployed resource properties:
resources:
- name: my-vm
type: compute.v1.instance
properties:
zone: us-central1-a
# ... other properties
outputs:
- name: vmIP
value: $(ref.my-vm.networkInterfaces[0].accessConfigs[0].natIP)
- name: vmName
value: $(ref.my-vm.name)
In this legacy example, the VM's external IP address and name are exposed as outputs. The $(ref.resource-name.property) syntax references specific attributes from the deployed resources.
Retrieving Output Values
If you are maintaining or auditing an existing deployment and need to view its published values, you can use the following legacy CLI command as a reference:
gcloud deployment-manager deployments describe my-deployment
The outputs appear in the command response, making them accessible for legacy scripts or migration documentation. Do not use this command to orchestrate new deployments.
Key Takeaway: Deployment outputs were used in legacy Google Cloud Deployment Manager configurations to explicitly expose important resource values, and understanding them is helpful when auditing, maintaining, or migrating existing infrastructure to Terraform or Infrastructure Manager.