GcpDmInfra · Waitlist
Support discontinued (in effect). Standard DM tickets auto-rejected unless migration-related or blockers.
Maximum support extension ends.
Deployment Manager turned down; all related APIs stop. Existing resources keep running.
Since Jun 30, 2026, new users can't enable the Deployment Manager V2 API or create a first deployment. Until turn-down, existing customers can still use DM "at your own risk".
Dates per Google Cloud "Deployment Manager deprecation" (last updated Sep 30, 2026). DM Convert is a Preview tool.
Deployment Manager support ended Apr 1, 2026, the maximum support extension ends Mar 31, 2027, and the service is turned down after Jun 30, 2027 — your existing resources keep running. Answer 5 quick questions — YAML, Jinja, or Python templates; composite types, type providers, or Actions; where your configs live; whether you rely on DM preview or rollback; and Infra Manager vs. self-managed Terraform. Get conversion feasibility, a manual-gap list, the Convert → import → abandon order, and a regression checklist. Never paste credentials, service account keys, project IDs, or configs.
Independent tool. Not affiliated with or endorsed by Google. · Not a GCP connector. Never paste credentials.
Problem
Per Google Cloud's "Deployment Manager deprecation" page, support was discontinued on Apr 1, 2026 — standard DM tickets are auto-rejected unless they are blockers or related to your migration to Infra Manager — and the maximum support extension ends on Mar 31, 2027. The service is turned down after Jun 30, 2027, when all related APIs stop. Resources created by Deployment Manager continue to function. The official path is DM Convert (Preview) → Terraform import → Infra Manager import → --delete-policy ABANDON, but composite types, Actions without declarative equivalents, and custom type providers aren't converted — and the default delete policy, DELETE, permanently deletes the underlying resources.
deployments delete with the default DELETE policy, or unlock an Infra Manager import with mismatched state--delete-policy ABANDON| Date | Status | What it means |
|---|---|---|
| Apr 1, 2026 | In effect | Support discontinued (in effect). Standard DM tickets auto-rejected unless migration-related or blockers. |
| Jun 30, 2026 | In effect | Since Jun 30, 2026, new users can't enable the Deployment Manager V2 API or create a first deployment. |
| Mar 31, 2027 | Support | Maximum support extension ends. |
| After Jun 30, 2027 | Turn-down | Deployment Manager turned down; all related APIs stop. Existing resources keep running. |
Until turn-down, existing customers can still use DM "at your own risk" through the console, the Google Cloud CLI, and the Deployment Manager V2 API — no new features, no non-critical fixes. Resources created by Deployment Manager continue to function and can be managed with standard Google Cloud tools. App Engine Flex customers not using DM are unaffected.
Solution
A Deployment Manager → Infra Manager / Terraform migration-readiness decision layer for platform and IaC teams still on Deployment Manager: your DM usage × advanced features × config storage × dependencies × target → convertibility + manual gaps + order + regression checklist. Not a replacement for Google Cloud docs, not a GCP connector, and not affiliated with Google.
Platform engineering, IaC / Terraform, and DevOps / SRE teams and cloud architects who still manage GCP resources with Google Cloud Deployment Manager — YAML configs with Jinja / Python templates, gcloud deployment-manager, and the Deployment Manager V2 API — and haven't moved to Infrastructure Manager (Infra Manager) or self-managed Terraform yet.
Support ended Apr 1, 2026 and the maximum support extension ends Mar 31, 2027; after Jun 30, 2027 the service is turned down. The official path (DM Convert in Preview → Terraform state import → Infra Manager import → ABANDON) leaves gaps: composite types, Actions without declarative equivalents, and custom type providers aren't converted; private Git needs a Cloud Build connection; state lives in Cloud Storage; rollback becomes a manual roll forward; and the default DM delete policy is DELETE.
Tick 5 questions → conversion feasibility, a manual-gap list, the DM Convert → Terraform import → Infra Manager import → abandon order (with official commands), and a regression checklist. Never asks for GCP credentials, service account keys, project / organization IDs, DM configs, or code; not a GCP connector.
Every deployment converted to Terraform and handed to Infra Manager or self-managed Terraform, then released from DM with --delete-policy ABANDON before the turn-down after Jun 30, 2027 — instead of deleting production resources with the default DELETE, or finding out in July 2027 that your infrastructure can no longer be updated with the old tool.
Features
Marketing points from the product hypothesis — for demand validation, not a formal spec promise.
You're already on "at your own risk". Need Google's help migrating? Before Mar 31, 2027. Everything converted, imported, and abandoned before the post–Jun 30, 2027 turn-down.
References, dependsOn, accessControl, iamMemberBinding convert; composite types and custom type providers don't; only Actions with declarative equivalents convert.
Composite types → Terraform modules; private Git → Cloud Build connection; rollback → manual roll-forward; preview → Infra Manager previews; no backend block; 2-hour apply timeout.
Expanded config → DM Convert → Terraform import → Infra Manager lock / import-statefile / unlock / preview → --delete-policy ABANDON.
Rehearse in a non-prod project, review every terraform plan, confirm "No changes" in Infra Manager preview, abandon, then confirm resources are still there.
| Your DM usage | DM Convert (Terraform) |
|---|---|
| Plain YAML, Jinja, Python templates | Converted — DM Convert reads YAML and Jinja / Python templates; you can take the expandedConfig from a live deployment's manifest |
References, dependsOn | Terraform references, depends_on |
accessControl (authoritative) | <resource_type>_iam_policy |
iamMemberBinding (non-authoritative) | <resource_type>_iam_member |
| Composite types | Not converted (deprecated) → write Terraform modules by hand |
Actions: insert / get / setIamPolicy | Converted to resource / data / *_iam_policy · *_iam_member |
| Actions: patch / delete / list, custom APIs | Not converted → handle manually |
| Custom type providers | Not converted (Actions defined by their APIs aren't converted) |
| Unsure about a resource type | Check the official supported list with --list_supported_types |
DM Convert is a Preview tool. It outputs Terraform configuration plus a Terraform import-command file (--output_tf_import_file); the Terraform state is produced when you run those imports. When converting from an expanded config, template parameters and loops are already expanded — to keep reuse, rewrite them as Terraform variables / modules yourself (inferred from the official flow; check after converting).
| DM concept | Infra Manager / Terraform approach |
|---|---|
| Composite types / reusable templates | Terraform modules (must be a valid root module; Infra Manager doesn't support templating / generation) |
| Configs in private Git | Connect the Git host and repo to Cloud Build (or the Developer Connect Git proxy) first, then use --git-source-repo |
| DM-internal state | Infra Manager stores it in Cloud Storage automatically; for self-managed Terraform, a Cloud Storage bucket is recommended; Infra Manager configs can't define a backend block |
| DM rollback | Manually roll forward with the Terraform configuration from a previous revision |
| DM preview | gcloud infra-manager previews create (Terraform plan) |
| Large deployments | Create / update time out after 2 hours, preview after 1 hour → split the configuration |
goog-dm label | After import, terraform plan shows the goog-dm label being removed (acceptable per the official example) |
Private Git repos work with Infra Manager once the Git host and repository are connected to Cloud Build — GitHub, GitHub Enterprise, GitLab, GitLab Enterprise, or the Developer Connect Git proxy. The deprecation page describes this as lacking "direct" support.
gcloud deployment-manager deployments describe DEPLOYMENT_NAME --format="value(deployment.manifest)"gcloud deployment-manager manifests describe MANIFEST_NAME --deployment DEPLOYMENT_NAME --format="value(expandedConfig)"--config deployment.yaml --output_format TF --output_file … --output_tf_import_file … --deployment_name … --project_id …terraform init, run the generated import file, then review every difference in terraform plan.gcloud infra-manager deployments apply) → gcloud infra-manager deployments lock → import-statefile + upload terraform.tfstate → upload the configuration → confirm state and configuration match → unlock → gcloud infra-manager previews create shows No changes.If state and configuration don't match, Infra Manager creates or deletes resources on unlock to match the state.
gcloud deployment-manager deployments delete DEPLOYMENT_NAME --delete-policy ABANDONNever use the default DELETE policy — it permanently deletes the underlying resources.
Examples always use PROJECT_ID / DEPLOYMENT_NAME placeholders — this page never accepts any ID. Commands and flags as written in Google Cloud's DM Convert, Infra Manager import, and Deleting deployments docs.
How it works
Three steps. No Google Cloud connection, no credentials.
YAML, Jinja, or Python? Composite types, type providers, or Actions? Where do configs live? Rely on DM preview or rollback? Infra Manager or self-managed Terraform?
Conversion feasibility, a manual-gap list, and your Mar 31 / Jun 30, 2027 timeline risk — each linked to Google Cloud docs.
The official order — DM Convert → Terraform import → Infra Manager import → --delete-policy ABANDON — plus a regression checklist. Never paste credentials, keys, IDs, or configs.
Use cases
If these situations sound familiar, join the waitlist to help us validate.
Composite types aren't converted — you need a list of Terraform modules to write by hand and steps to compare them.
The conversion output is the expanded resources — decide whether to refactor into modules / variables, and split configs to stay under Infra Manager's 2-hour timeout.
Infra Manager needs a Cloud Build connection first — you need the prerequisite checklist.
You need to switch to Infra Manager previews and a roll-forward runbook.
Decide between Infra Manager and self-managed Terraform (state in Cloud Storage, run in Cloud Build), and schedule per-deployment Convert → import → abandon batches.
Know which Actions become a resource / data and which must be handled manually.
Public signals
Official Google Cloud documentation only — public signals, not endorsements. No customer quotes, logos, or invented metrics.
FAQ
No. GcpDmInfra is independent and not affiliated with or endorsed by Google. Everything cites official Google Cloud docs with links.
Per Google Cloud docs, resources created by Deployment Manager continue to function and can be managed with standard Google Cloud tools — just not with Deployment Manager or gcloud deployment-manager.
Mar 31, 2027 is when the maximum support extension ends. After Jun 30, 2027, the service is turned down and all related APIs stop. Support itself ended Apr 1, 2026.
No. Composite types aren't converted, only Actions with declarative equivalents are, and custom type providers aren't. DM Convert is also a Preview tool.
Yes, once you connect your Git host and repository to Cloud Build (per Infra Manager's deploy docs). The deprecation page describes this as lacking "direct" support.
Use --delete-policy ABANDON. The default DELETE policy permanently deletes the underlying resources.
No. Never asked, never held, never stored. We don't connect to your Google Cloud projects.
No. The MVP is a static questionnaire + lists + order + waitlist.
Waitlist invites go out in batches by email. No fake launch date.
GcpDmInfra is an independent tool, not affiliated with or endorsed by Google. Google Cloud is a trademark of Google LLC.
Waitlist
Leave your work email for GcpDmInfra early access and launch notes. Email plus optional checkboxes and dropdowns only — there is no free-text field anywhere on this form.
We'll email early-access invites and launch updates in batches (no promised launch date). Check your inbox for a confirmation email if enabled. Unsubscribe anytime.