cdktf deploy errors when using Terraform Cloud remote backend
See original GitHub issueWhen using Terraform Cloud the cdktf deploy
command fails to save generated plan as it is not supported by the remote backend that has remote plan/apply turned on.
Error: Saving a generated plan is currently not supported
The "remote" backend does not support saving the generated execution plan
locally at this time.
Warning: Render methods should be a pure function of props and state; triggering nested component updates from render is not allowed. If necessary, trigger nested updates in componentDidUpdate.
This is currently not supported by Terraform. See: https://github.com/hashicorp/terraform/issues/22779
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Deploy Applications with CDK for Terraform
Deploy an application on Kubernetes with CDK for Terraform (CDKTF). ... Terraform state locally, rather than in a remote backend such as Terraform...
Read more >CDK for Terraform (CDKTF) on AWS: How to Configure an ...
Deploying an S3 bucket, DynamoDB table and configuring an S3 remote backend. Learning how to read/use AWS Provider Submodules and Construct Hub ...
Read more >Store Terraform state in Azure Storage
Configure remote state storage account. Before you use Azure Storage as a backend, you must create a storage account. Run the following commands ......
Read more >hashicorp-terraform/Lobby - Gitter
In my local environment I can run cdktf fine with our terraform enterprise server as the remote backend. however, when I deploy in...
Read more >Errors during deployment to AWS using Terraform (cdktf)
Your diagnosis seems right, there might be some stray resources left behind due to an aborted / unfinished Terraform run.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have added a note in our documentation here.
For further clarification: This applies to pre-existing workspaces which were setup for remote execution. The default
cdktf init
workflow - where a new workspace is created - is not affected by this, since the workspace will be properly setup for local execution.