Terraform and Infrastructure Manager

To work with Infrastructure Manager (Infra Manager), you should be familiar with Terraform. To learn more about Terraform, start with What is Terraform?.

Infra Manager deploys infrastructure resources and configurations that are defined in a Terraform configuration. These configurations can consist of multiple files and directories, but their entrypoint must be a Terraform root module.

Infra Manager uses the term blueprint to refer to a Terraform configuration.

To learn more about Terraform with Google Cloud, see Terraform on Google Cloud.

Terraform modules for Google Cloud

For a set of modules to provision Google Cloud resources, see Terraform blueprints and modules for Google Cloud.

You can also create your own Terraform modules for Google Cloud. For more details, see Creating Modules.

Supported Terraform versions

Infra Manager supports the following Terraform versions:

For information about the features introduced in each Terraform release, see the HashiCorp Terraform documentation and Terraform releases.

You can specify the version of Terraform that Infra Manager uses when you create a deployment, update a deployment, or preview a deployment in the Google Cloud console or by using the --tf-version-constraint flag in the gcloud CLI.

If you don't specify a version of Terraform when creating a new deployment or preview, Infra Manager uses the latest supported free tier version (1.5.7) by default. To use a paid version (such as 1.16.5), you must explicitly specify the version constraint.

When updating a deployment, you can upgrade to a later Terraform version, but you cannot downgrade to an earlier supported version. For information about Terraform version deprecation, see the Terraform version management policy documentation.

To view the version of Terraform that was used to create a specific deployment or revision, see View details of a deployment and View details of a revision.

Licensing and pricing for Terraform versions

Terraform versions 1.5.7 and earlier are distributed as open source under the Mozilla Public License (MPL 2.0) and are available in the Free tier with no Infra Manager management fee.

Terraform version 1.16.5 is distributed under the Business Source License (BUSL) and is offered as a Paid version in Infra Manager. Using a paid Terraform version incurs deployment and management charges based on the number of resources managed by Infra Manager:

• Free tier allowance: Each billing account receives a free tier allowance of up to 500 resources per month at no charge.

• Usage charges: Beyond the 500-resource monthly free tier allowance, resources managed by deployments that use a paid Terraform version incur resource management charges that are metered hourly per resource.

• Previews are not charged: Paid Terraform versions (such as 1.16.5) incur charges only for Infra Manager deployments, not for deployment previews.

For more information about pricing, see Infrastructure Manager pricing.

Constraints on Terraform configurations

To use Infrastructure Manager to deploy a Terraform configuration, the configuration has the following constraints:

• Don't include personally identifiable or sensitive information in Terraform configuration values. For more information, see Terraform configuration values and sensitive data.
• A valid Terraform root module must be provided. Templating or generation of Terraform is not supported.
• The configuration should be actuatable by a supported version of Terraform.
• Backend blocks shouldn't be defined.
• We don't recommend using provisioners. When possible, use a different solution. For more information about this recommendation, see Provisioners are a Last Resort. If you are using provisioners, note that the Infra Manager runtime environment can change at any time.

Terraform configuration values and sensitive data

Don't include personally identifiable or sensitive information in Terraform configuration values.

The documentation for the Google Cloud provider indicates configuration values that can potentially include sensitive information.

For example, the resource google_storage_bucket_object allows creation of a Cloud Storage object using the content argument. This argument is labeled as sensitive on the google_storage_bucket_object page of the Google Cloud Provider documentation.

You can use these labels to help guide you as you create Terraform configurations or as you review an existing Terraform configuration before use.

See the Google Cloud Privacy Notice for information on how Google Cloud processes personal information it collects or generates during the provision and administration of the Cloud Services.

Use the Terraform provider for Google Cloud

Optionally, you can use gcloud CLI to configure deployments and previews to use Infra Manager maintained Terraform providers for Google Cloud.

Infra Manager supports Terraform providers for Google Cloud:

• google
• google-beta

Omit this field to use the HashiCorp-maintained Terraform provider for Google Cloud.

To learn how to specify the use of a Infra Manager maintained Terraform provider, see Deploy infrastructure using Infrastructure Manager, Update a deployment, or Preview a deployment.

Check supported versions of the provider

To check the versions of a Terraform provider for Google Cloud that Infra Manager supports, view the manifest.json in the Infra Manager maintained Cloud Storage bucket associated with the region of your deployment in the format:

https://storage.googleapis.com/LOCATION-im-providers/hashicorp/PROVIDER_VERSION/manifest.json

You can find a complete list of supported versions within the versions field of the manifest.json file.

For example, if your deployment is located in the africa-south1 region and you are using the google-beta provider, navigate to https://storage.googleapis.com/africa-south1-im-providers/hashicorp/google-beta/manifest.json to view available regions.

What's next

• Learn more about Infrastructure Manager.
• Create a deployment.
• Update a deployment.
• View the state of a deployment.
• Delete a deployment.