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.

This Feature Toggle is disabled in 2.x but enabled by default from 3.0 onwards, and is intended to avoid the unintentional destruction of resources managed outside of Terraform (for example, provisioned …

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 afterwards.

The root issue lies with the order in which Terraform itself evaluates the provider blocks vs. actual resources. Please refer to this section of Terraform docs for further explanation.

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 …

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 for more …

Read more about sensitive values in the Terraform documentation. We are planning to research migration to Plugin Framework and we will investigate if the limitations coming from Plugin SDK can …

When working with local files, Terraform will detect the resource as having been deleted each time a configuration is applied on a new machine where the file is not present and will generate a diff to re …

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 …

Use the Databricks Terraform provider to interact with almost all of Databricks resources. If you're new to Databricks, please follow guide to create a workspace on Azure or AWS and then this workspace …