Known Issues and Workarounds
- Error: No value for required variable in Terraform Cloud or Terraform Enterprise
- Terraform Enterprise restore from S3 snapshot fails with "checksum error:" or "InvalidObjectState"
- Unexpected \n in plan output using yamlencode() with Terraform
- Terraform State version compatibility-v0.13.6-v1.0.x
- How to minify the output of JSON files
- v1.1.0/v1.1.1 Bug: Terraform applied no changes and unexpectedly emptied the State File
- Destroy Runs fail with "Failed to marshal plan to json: error marshaling prior state: unsupported attribute"
- Error While Creating a Private Module Using the API
- Terraform SAML Login Error: Username has already been taken
- How-to disable Terraform version checks when making calls to another state configuration
- Error fetching data: Vault has encountered an error retrieving a secret.
- Error initializing storage of type postgresql: failed to check for native upsert: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
- Resolve Terraform Error: 'Module has no tags'
- Importing existing Resource(s) into a Remote State Managed by Terraform Cloud/Enterprise may fail with error "Invalid provider configuration. The configuration for provider depends on values that cannot be determined until apply."
- Runs In Terraform Cloud VCS linked workspaces may fail with "Invalid run parameters" error
- Best practices around running Terraform Cloud agents behind GCP NAT (SNAT)
- Possible side-effects of using WAF (Web Application Firewall) with Terraform Enterprise. ( Cloud Armor, Azure WAF, Amazon WAF)
- Known issues with default_tags in the Terraform AWS Provider
- Issue publishing modules in Terraform Cloud Private Module Registry
- MTU Configuration for Custom Networks
- TFE: import Terraform resources when VCS or API driven approach is used
- "Error tagging stats.gauges.replicated" and "Error tagging stats.statsd" continually repeated in logs
- TF logging in Terraform Enterprise showing [TRACE] level logging despite not being set.
- Operation failed: failed generating plan JSON: failed running command (exit 2) on Terraform v1.0.1
- Failure To Connect Version Control System Provider To Terraform Enterprise
- PostgreSQL 12 Upgrade Error: database user hashicorp is not the install user
- Tuning ulimit values for Terraform Enterprise
- PostgreSQL 12 Upgrade Error: Timeout waiting for event PostgreSQL Upgraded
- Terraform apply failed with `no suitable version installed` or `Could not load plugin` in Terraform Enterprise
- Unmet Start Requirement on New Terraform Enterprise Active-Active Install