Type Providers and External APIs
Important Notice: Google Cloud Deployment Manager reached end of support on March 31, 2026. This content is provided strictly as a legacy reference for maintaining existing deployments. Direct all new infrastructure work to Google Cloud Infrastructure Manager or Terraform. Do not use gcloud deployment-manager commands to create new deployments; they should be treated as legacy reference material only.
What You'll Learn
You'll discover how legacy Google Cloud Deployment Manager setups extended beyond native GCP resources by integrating external REST APIs through Type Providers.
The Core Concept
In existing legacy templates, Deployment Manager was frequently used to create native GCP resources like compute instances and storage buckets. However, architectures often needed to manage resources that weren't GCP services—such as an external monitoring tool, a third-party database service, or another cloud provider's API.
Type Providers were Deployment Manager's mechanism for connecting to any external REST API that supported CRUD operations (Create, Read, Update, Delete). Think of them as adapters that translated Deployment Manager's configuration language into API calls for external systems.
How It Works
A Type Provider is defined as a resource within a legacy Deployment Manager configuration. It relies on:
- API endpoint URL – where the external service lives.
- API descriptor – typically an OpenAPI (Swagger) specification that describes available operations and paths.
- Authentication details – how to securely authenticate with the external API.
Once registered in an existing deployment, configurations could reference resources from that external API in YAML just like native GCP resources. Deployment Manager handled the HTTP requests, response parsing, and state tracking automatically.
Legacy Context
Type Providers allowed teams to manage their entire infrastructure—GCP and external dependencies—in a single Deployment Manager template. Modern infrastructure-as-code platforms have since adopted this pattern. If you encounter Type Providers in legacy codebases, understand that their purpose was to unify configuration and dependency management. For modern architectures, Terraform providers now fulfill this identical role.
Key Takeaway:
Type Providers extended legacy Google Cloud Deployment Manager deployments by wrapping external REST APIs to manage non-GCP resources alongside native services, but all new external integrations and infrastructure work must now use Google Cloud Infrastructure Manager or Terraform.