Articles in this section
- AWS S3 Bucket Policy not found
- How to find the right documentation for any Terraform version
- TFE - The runs are stuck in Plan Queued
- Vault-Azure Credentials integration Bug & Solution [Error building account: Error getting authenticated object ID: Error listing Service Principals: autorest.DetailedError]
- "Error attempting to upload bundle: undefined" received during airgap install
- "Error: idna: disallowed rune U+002F" Encountered When Using the TFE Provider
- "Error: port portion contains non-digit characters" Encountered When Using the TFE Provider
- "Host key verification failed" error in a Terraform Enterprise run when attempting to ingress Terraform modules via Git over SSH.
- "no migration found for version" Error Encountered After Using the Restore API to Restore Terraform Enterprise
- Adding a SAML User to a Team Does Not Take Effect Immediately
Related articles
- Terraform runs don't execute in Terraform Enterprise
- How to resolve incorrect Geoblocking on HashiCorp platforms
- How to Import Resources into a Remote State Managed by Terraform Cloud
- How to set "remote" backend partial configuration to manage different environments with Terraform Cloud
- Using the remote backend and Terraform CLI to run plan and state operations locally (Terraform <= v1.0.11)
Problem: You cannot use
-outfile
with a remote backend, but may want the execution plan.Solution: You can retrieve the
json execution plan
via this API call, but it requires admin permissions on the workspace.You can get the
plan-id
required by using the runs API and then use that plan to get the json execution planFor example the below curl command works when you are using an admin token
Note : The JSON plan contains potentially sensitive information, including the values of sensitive variables and copies of the prior and post-refresh state. This is why the JSON plan isn't accessible without elevated permissions.
Documentation:
Show a plan
Get run details