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 provider gives Terraform the ability to work with VMware vSphere. This provider can be used to manage many aspects of a vSphere environment, including virtual machines, standard and …

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 …

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 …

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.

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 learn the basics of Terraform using this provider, follow the hands-on get started tutorials. Interested in the provider's latest features, or want to make sure you're up to date?

Once this parameter is set to true, a successful terraform apply run before a destroy is required to update this value in the resource state. Without a successful terraform apply after this …

We recommend using either a Service Principal or Managed Service Identity when running Terraform non-interactively (such as when running Terraform in a CI server) - and …

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 …