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.

RegistryPlease enable Javascript to use this application

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 …

The root issue lies with the order in which Terraform itself evaluates the provider blocks vs. actual resources. Please refer to this section of Terraform docs for further explanation.

When working with local files, Terraform will detect the resource as having been deleted each time a configuration is applied on a new machine where the file is not present and will generate a diff to re …

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 …

Overview Documentation Use ProviderReport an issue

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.

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 …

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 …