Allow per-stack state file name via TF_STATE_FILE_NAME#3
Open
Allow per-stack state file name via TF_STATE_FILE_NAME#3
Conversation
When a single repo contains multiple Terraform stacks (e.g. the sub-stacks under terraform-server), each stack needs its own state file under the same S3 backend bucket. The original fivexl tf.sh supports this through a TF_STATE_FILE_NAME env var (defaulting to main.tfstate), sourced from a per-stack tf.sh.env file. Our Python rewrite hardcoded main.tfstate, which would have caused every stack in the same repo to collide on one state file. Plumb a state_file_name argument through TfBackend and resolve it from TF_STATE_FILE_NAME (default main.tfstate) when building the backend. The variable can be set in the shell or in tf.env, which tf already loads on startup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a single repo contains multiple Terraform stacks (e.g. the sub-stacks under terraform-server), each stack needs its own state file under the same S3 backend bucket. The original fivexl tf.sh supports this through a TF_STATE_FILE_NAME env var (defaulting to main.tfstate), sourced from a per-stack tf.sh.env file. Our Python rewrite hardcoded main.tfstate, which would have caused every stack in the same repo to collide on one state file.
Plumb a state_file_name argument through TfBackend and resolve it from TF_STATE_FILE_NAME (default main.tfstate) when building the backend. The variable can be set in the shell or in tf.env, which tf already loads on startup.