Docs overview | hashicorp/aws | Terraform | Terraform Registry
By default, the underlying AWS client used by the Terraform AWS Provider creates requests with User-Agent headers including information about Terraform and AWS SDK for Go versions.
Docs overview | vmware/vsphere - Terraform Registry
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 …
azurerm_resource_group | Resources - Terraform Registry
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 …
Resources | hashicorp/aws - Terraform Registry
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.
Docs overview | hashicorp/google - Terraform Registry
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 …
Docs overview | hashicorp/kubernetes - Terraform Registry
Terraform providers for various cloud providers feature resources to spin up managed Kubernetes clusters on services such as EKS, AKS and GKE. Such resources (or data-sources) will have …
Docs overview | microsoft/fabric - Terraform Registry
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 …
Azure Resource Manager: 4.0 Upgrade Guide - Terraform Registry
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 …
Resources | hashicorp/aws - Terraform Registry
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 apply your …
aws_instance | Resources | hashicorp/aws - Terraform Registry
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 parameter is …