Closed frank-bee closed 12 months ago
See here, how terragrunt handles this feature https://terragrunt.gruntwork.io/docs/features/keep-your-remote-state-configuration-dry/#create-remote-state-and-locking-resources-automatically
Thank you @frank-bee This seems to be a great feature that improves UX of the controller a lot.
Closing for now as it's out of scope for our immediate plans. Will reopen should this change.
Currently the state is either stored in a secret, which is cumbersome to backup / version. Or it is stored as an external backend ( e.g. on s3) which is cumbersome to setup ( a lot of code duplication , many state files potentially ).
Proposal: Allow configuring the backend on controller level, everything besides the "key", e.g. :
And create the actual state files ( "key"s ) automatically. (Like tools like terragrunt allow this, If I remember that correctly)
Even the state lock table ( in AWS it is a dynamo table ) could be created automatically.
=========
User story:
As a Terraform Controller developer, I'd like to simplify the backend management for Terraform Controller, so that users can configure the backend on the controller level and have state files managed more easily.
Acceptance Criteria: