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?

Importing an existing repository and running terraform plan will detect a difference on the initialization block. The plan and apply will then attempt to update the repository based on the …

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 …

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 …

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.

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 …

Terraform uses Shared Key Authorisation to provision Storage Containers, Blobs and other items - when Shared Key Access is disabled, you will need to enable the storage_use_azuread flag …

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 …

Terraform primarily deals with remote resources which are able to outlive a single Terraform run, and so local resources can sometimes violate its assumptions. The resources here are best …

As Sets are stored using a hash, if one value is added or removed from the Set, Terraform considers the entire list of objects changed and the plan shows that it is removing every value …