Handle Not Existing Org / Workspaces in Terraform Cloud

[skorfmann]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When using Terraform Cloud as remote runner, cdktf will zip the ./cdktf.out folder contents and uploads it to the TerraformCloud API. The entire diff / deploy / destroy cycle is then running remotely. That's done in via the TerraformCloud handler within the cdktf-cli package, which is relying on this api wrapper. All interactions with the Terraform Cloud API are relying on valid credentials and correct configuration for the organization / workspace.

The organization and workspace configuration is sourced from the synthesized stack. When one the values is misconfigured, it looks like the raw error from axios is being printed out. This should be more expressive and actionable to the user.

I think it would make sense to add some basic error handling to the TerraformCloud class, which takes care of making the errors more expressive.

References

• Terraform Cloud Support #449

[ansgarm]

Resolved via #626

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.