terraform-cdk icon indicating copy to clipboard operation
terraform-cdk copied to clipboard

Design: Improved TFC integration for multi-stack projects

Open DanielMSchmidt opened this issue 3 years ago • 5 comments

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

Currently we only create the first stack for users using TFC when running init, all other stacks need to be created manually. The goal of this issue is to find a nicer way to manage multiple workspaces (and their secrets / run triggers / ...?) and propose a solution / vision for how we want to tackle this problem.

References

  • https://github.com/DanielMSchmidt/cdktf-multi-stack-tfe is a user-land approach to this

DanielMSchmidt avatar Apr 21 '22 14:04 DanielMSchmidt

This issue is slightly related: https://github.com/hashicorp/terraform-cdk/issues/670

ansgarm avatar Apr 21 '22 14:04 ansgarm

Yeah, though I'd like to include more day2 things here in addition to "just" auto creating like managing secrets etc.

DanielMSchmidt avatar Apr 22 '22 08:04 DanielMSchmidt

@DanielMSchmidt The following dependency for supporting TFC! I am not sure why this hasn't been available since day 1 - don't you guys use Terraform v1.1+ and TFC at HashiCorp?!

nikolay avatar May 24 '22 19:05 nikolay

Sorry there is some misunderstanding happening here, we support TFC. The issue you are referencing is about a the current way of using terraform cloud (through the remote backend) is being deprecated by Terraform, so we should start supporting the new (through the cloud backend).

DanielMSchmidt avatar May 24 '22 20:05 DanielMSchmidt

@DanielMSchmidt It behaves differently, it's not just deprecation. By using "remote", you can't override sensitive remote variable - you can only do this with "cloud" backend. The "remote" backend comes with a bug, which, for some strange reason, was only fixed in "cloud".

nikolay avatar May 25 '22 03:05 nikolay

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.

github-actions[bot] avatar Aug 13 '23 01:08 github-actions[bot]