Terraform Registry
RegistryPlease enable Javascript to use this application
Docs overview | Telmate/proxmox - Terraform Registry
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 …
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 …
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 …
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, …
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 …
azuread_application_registration - Terraform Registry
id - The Terraform resource ID for the application, for use when referencing this resource in your Terraform configuration. object_id - The object ID of the application within the tenant.
Browse Modules - Terraform Registry
Terraform module, which takes care of a lot of AWS Lambda/serverless tasks (build dependencies, packages, updates, deployments) in countless combinations 🇺🇦
Docs overview | DataDog/datadog - Terraform Registry
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 …