Cloud Deployment Manager V2 API

Name: Cloud Deployment Manager V2 API API
Brand: Cloud Deployment Manager V2 API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureComputeoauth218 EndpointsREST

For Agents

Provision and manage Google Cloud infrastructure as code via templated deployments, with preview, manifest, and resource introspection.

Quickstart

Get started with Cloud Deployment Manager V2 API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy a Google Cloud template"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Deployment Manager V2 API API.

Insert, update, and delete deployments composed of Google Cloud resources

Preview deployment changes before applying them via cancelPreview and stop operations

Inspect deployment manifests to verify template expansion and resource configuration

List and retrieve resources owned by a deployment to track provisioned infrastructure

GET STARTED

Start building with Cloud Deployment Manager V2 API API

Explore with Jentic

View OpenAPI Document

Use for: I need to deploy a new set of Google Cloud resources from a template, Preview the changes a deployment will make before applying them, List all deployments in a Google Cloud project, Retrieve the manifest for a deployment to inspect expanded resources

Not supported: Does not handle container orchestration, CI build pipelines, or runtime application monitoring — use for declarative Google Cloud resource provisioning only.

Google Cloud Deployment Manager lets you declaratively configure, deploy, and update Google Cloud resources using YAML or Jinja/Python templates. Manage deployments, manifests, and resources programmatically across projects, with support for previewing changes before applying them. Templates can compose multiple Cloud services (Compute Engine, Cloud Storage, Cloud SQL) into a single repeatable deployment. Built for teams running infrastructure-as-code workflows on Google Cloud.

Use Cases

Patterns agents use Cloud Deployment Manager V2 API API for, with concrete tasks.

★ Infrastructure-as-Code Rollouts

Define Google Cloud infrastructure as Deployment Manager templates and apply them via the deployments.insert endpoint. Engineers commit YAML or Jinja templates to source control, run a preview to surface diffs, then apply the deployment to provision Compute Engine instances, networks, storage buckets, and IAM bindings in one transaction. Typical multi-service stacks roll out in 2-10 minutes.

Insert a new deployment named web-stack using a YAML template that creates one Compute Engine VM and one Cloud Storage bucket, then poll the operation until done.

Deployment Drift Auditing

Use the manifests and resources endpoints to compare what a deployment claims to manage versus what currently exists in the project. Auditors call deployments.get plus manifests.get to retrieve the expanded template, then list resources to verify each is still in the intended state. Useful for compliance reviews and pre-merge checks on platform repos.

Get the active manifest for deployment prod-network and list all resources it owns, then return any resource whose state is not COMPLETED.

Safe Update Previews

Run deployments.update with the preview flag set to model changes without applying them. Platform teams use this to surface destructive changes (resource recreation, IAM removal) before approving a merge. If the preview shows undesired changes, call cancelPreview to discard; otherwise re-run update without preview to apply.

Update deployment data-pipeline with preview=true using a new template, then list the manifest changes and abort if any resource will be deleted.

Agent-Driven Environment Bootstrap

Through Jentic, an AI agent can search for the deployment insert operation, load its schema, and bootstrap an entire test environment from a natural-language brief. The agent supplies a project ID and template body, and Jentic executes the call against Deployment Manager with scoped OAuth credentials managed by the MAXsystem vault.

Use Jentic to search 'create a Google Cloud deployment from a template', load the schema, and execute deployments.insert for project test-env-42 with a Jinja template body.

Key Endpoints

18 endpoints — google cloud deployment manager lets you declaratively configure, deploy, and update google cloud resources using yaml or jinja/python templates.

METHOD

PATH

DESCRIPTION

GET

/deploymentmanager/v2/projects/{project}/global/deployments

List all deployments in a project

POST

/deploymentmanager/v2/projects/{project}/global/deployments

Create a new deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Get a specific deployment

DELETE

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Delete a deployment and its resources

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/cancelPreview

Cancel a deployment preview

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/stop

Stop an in-progress deployment update

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/resources

List resources owned by a deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/manifests/{manifest}

Get an expanded deployment manifest

GET

/deploymentmanager/v2/projects/{project}/global/deployments

List all deployments in a project

POST

/deploymentmanager/v2/projects/{project}/global/deployments

Create a new deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Get a specific deployment

DELETE

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Delete a deployment and its resources

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/cancelPreview

Cancel a deployment preview

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth tokens for Deployment Manager are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived tokens with deployment-manager scope only — raw service-account JSON never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'deploy a Google Cloud template') and Jentic returns the matching deployments.insert operation with its parameter schema, so the agent can call it without browsing the Discovery REST docs.

Time to first call

Direct Deployment Manager integration: 1-2 days for OAuth setup, scope configuration, and operation polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Build API

Run CI/CD pipelines that produce artifacts, then use Deployment Manager to roll them out

Choose Cloud Build when the agent needs to build container images or run tests; pair it with Deployment Manager for the rollout step.

Complementary

Compute Engine API

Direct VM, network, and disk management without templates

Use Compute Engine directly when the agent needs to mutate one resource imperatively; use Deployment Manager when changes should be templated and reproducible.

Alternative

Cloud Resource Manager API

Project, folder, and organization management — coarser than Deployment Manager

Choose Resource Manager for project/folder lifecycle operations; choose Deployment Manager for resource-level provisioning inside a project.

FAQs

Specific to using Cloud Deployment Manager V2 API API through Jentic.

What authentication does the Cloud Deployment Manager API use?

The API uses Google OAuth 2.0 with the deployment-manager and cloud-platform scopes. Through Jentic, OAuth tokens are stored encrypted in the MAXsystem vault and scoped per agent run, so raw service-account keys never enter the agent's context.

Can I preview a deployment before applying it with Cloud Deployment Manager?

Yes. Call deployments.update or deployments.insert with the preview parameter set to true. Deployment Manager expands the template and produces a manifest plus a list of intended resource changes without modifying live resources, and cancelPreview discards the preview.

What are the rate limits for the Cloud Deployment Manager API?

Deployment Manager applies Google Cloud per-project quotas: writes (insert, update, delete) are rate-limited per minute and total deployments per project are capped. Check your project quota under IAM and Admin to view current limits.

How do I list resources in a deployment through Jentic?

Search 'list resources in a Google Cloud deployment', load the schema for the resources.list endpoint at /deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/resources, then execute it with your project ID and deployment name. Jentic returns the parsed resource array.

Does Cloud Deployment Manager support rollback?

There is no first-class rollback endpoint. To revert, call deployments.update with the previous template body, or stop an in-progress deployment via the deployments.stop endpoint to halt further changes.

Is the Cloud Deployment Manager API free?

Deployment Manager itself has no charge. You pay for the underlying Google Cloud resources the deployments create (Compute Engine, Cloud Storage, Cloud SQL, etc.) at standard GCP rates.