The Terraform Registry makes it easy to use any provider or module. To use a provider or module from this registry, just add it to your configuration; when you run `terraform init`, Terraform will …

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 …

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 …

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 …

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 …

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 …

Terraform module, which takes care of a lot of AWS Lambda/serverless tasks (build dependencies, packages, updates, deployments) in countless combinations 🇺🇦

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 …

A Terraform provider to manage Portainer resources via its REST API using Terraform. It supports provisioning and configuration of Portainer users and will be extended to support other objects such …