Skip to content

Google Cloud Platform Provider

The Google provider is used to configure your Google Cloud Platform infrastructure.

To learn the basics of Terraform using this provider, follow the hands-on get started tutorials. For more involved examples, try provisioning a GKE cluster and deploying Consul-backed Vault into it using Terraform Cloud.

Already experienced with Terraform? Check out the Getting Started page for a short introduction to using Terraform with Google Cloud Platform.

Example Usage

A typical provider configuration will look something like:

/*Provider bindings are generated by running cdktf get.
See https://cdk.tf/provider-generation for more details.*/
import * as google from "./.gen/providers/google";
/*The following providers are missing schema information and might need manual adjustments to synthesize correctly: google.
For a more precise conversion please use the --provider flag in convert.*/
new google.provider.GoogleProvider(this, "google", {
  project: "my-project-id",
  region: "us-central1",
});

See the provider reference page for details on authentication and configuring the provider.

Take advantage of Modules to simplify your config by browsing the Module Registry for GCP modules.

The Google provider is jointly maintained by:

If you have configuration questions, or general questions about using the provider, try checking out:

Releases

Interested in the provider's latest features, or want to make sure you're up to date? Check out the google provider Releases and the [googleBeta provider Releases](https://github.com/hashicorp/terraform-provider-google-beta/releases for release notes and additional information.

Per Terraform Provider Versioning, the Google provider follows semantic versioning.

In practice, patch / bugfix-only releases of the provider are infrequent. Most provider releases are either minor or major releases.

Minor Releases

The Google provider currently aims to publish a minor release every week, although the timing of individual releases may differ if required by the provider team.

Major Releases

The Google provider publishes major releases roughly yearly. An upgrade guide will be published to help ease you through the transition between the prior releases series and the new major release.

During major releases, all current deprecation warnings will be resolved, removing the field in question unless the deprecation warning message specifies another resolution.

Before a major release, deprecation warnings don't require immediate action. The provider team aims to surface deprecation warnings early in a major release lifecycle to give users plenty of time to safely update their configs.

Features and Bug Requests

The Google provider's bugs and feature requests can be found in the GitHub repo issues. Please avoid "me too" or "+1" comments. Instead, use a thumbs up reaction on enhancement requests. Provider maintainers will often prioritize work based on the number of thumbs on an issue.

Community input is appreciated on outstanding issues! We love to hear what use cases you have for new features, and want to provide the best possible experience for you using the Google provider.

If you have a bug or feature request without an existing issue

The provider maintainers will often use the assignee field on an issue to mark who is working on it.

  • An issue assigned to an individual maintainer indicates that maintainer is working on the issue
  • An issue assigned to hashibot indicates a member of the community has taken on the issue!

Argument reference

See the provider reference page for details on configuring the provider.

Contributing

If you'd like to help extend the Google provider, we gladly accept community contributions! Development on the providers is done through the Magic Modules repository. Our full contribution guide is available on the Magic Modules Documentation Site