The Terraform Registry makes it easy to use any provider or module. To use a provider or module from this registry, just add it to your configuration; when you run `terraform init`, Terraform will …

To ensure security, it's best practice to create a dedicated user and role for Terraform instead of using cluster-wide Administrator rights. The particular privileges required may change but here is a suitable …

The provider needs to be configured with the proper credentials before it can be used. It requires terraform 0.12 or later. Try the hands-on tutorial on the Datadog provider on the HashiCorp Learn …

When upgrading to version 4.0 of the Azure Provider, we recommend upgrading to the latest version of Terraform Core (which can be found here). This guide will continue to receive updates as we …

Once the provider is configured, you can apply the Kubernetes resources defined in your Terraform config file. The following is an example Terraform config file containing a few Kubernetes resources.

This Terraform resource is specifically designed to provision the infrastructure for a Function App, which can host one or more individual functions.

We recommend using either a Service Principal or Managed Identity when running Terraform non-interactively (such as when running Terraform in a CI/CD pipeline), and authenticating using the …

Identity Schema Required arn (String) Amazon Resource Name (ARN) of the load balancer. In Terraform v1.5.0 and later, use an import block to import LBs using their ARN. For example:

Usage with Postcondition Precondition and Postcondition checks are available with Terraform v1.2.0 and later.

This is a terraform provider plugin for managing Snowflake accounts. Coverage is focused on part of Snowflake related to access control. Example Provider Configuration This is an example …