RegistryPlease enable Javascript to use this application

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 is a suitable …

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 Learn …

Once the provider is configured, you can apply the Kubernetes resources defined in your Terraform config file. The following is an example Terraform config file containing a few Kubernetes resources.

Usage with Postcondition Precondition and Postcondition checks are available with Terraform v1.2.0 and later.

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 …

by: hashicorp Template by: hashicorp HCP Terraform by: hashicorp Tfmigrate by: hashicorp

terraform import azurerm_private_endpoint.example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/Microsoft.Network/privateEndpoints/endpoint1

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 in the Provider …

Terraform will import this resource with force_destroy set to false in state. If you've set it to true in config, run terraform apply to update the value set in state. If you delete this resource before updating the …