Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

Deployment Manager

Competitor mapping for Google Cloud Platform.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Google Cloud Platform
Service term
Deployment Manager
Provider documentation
External reference

Behavioral divergences

Deployment Manager

Quake AI concept: Automation

  • Uses YAML configurations with optional Jinja2/Python templates expanded server-side; Quake AI offers Heat (legacy, HOT/YAML) and recommends OpenTofu (HCL) for new work.
  • Resource types named as service.v1.resource (e.g., compute.v1.instance) tied to GCP APIs, vs OpenStack prefixed types like OS::Nova::Server.
  • Single integrated GCP service (no separate API/engine processes); Heat has a multi-service architecture (heat-api, heat-engine) but is legacy. OpenTofu runs client-side with no server component.
  • No additional service fee; bills only for deployed GCP resources, same as OpenStack resources billing via provider.

Documentation

Related

Diverges from (incoming)

Citations

  1. Google Cloud Platform
  2. Google Cloud Platform

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.