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 …

Hard-coded credentials are not recommended in any Terraform configuration and risks secret leakage should this file ever be committed to a public version control system.

retain_on_delete (Optional) - Disables the distribution instead of deleting it when destroying the resource through Terraform. If this is set, the distribution needs to be deleted manually …

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 …

You can fix the problem two ways: 1) updating the function's role to another role and then updating it back again to the recreated role, or 2) by using Terraform to taint the function and …

To use the provider you can download the binaries from Releases to your local file system and configure Terraform to use your local mirror. See the Explicit Installation Method Configuration …

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

Version 6.0.0 of the AWS provider for Terraform is a major release and includes changes that you need to consider when upgrading. This guide will help with that process and focuses only on …

kubernetes_deployment A Deployment ensures that a specified number of pod “replicas” are running at any one time. In other words, a Deployment makes sure that a pod or …

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 …