Repository navigation
Let one repo deploy several components, each with its own state - #35
Merged
Merged
Conversation
tf keyed the statefile, drift file, Kosli flow and drift concurrency group on the repository name. A repo that deploys several components (eg cyber-dojo/web: web, creator, dashboard) had every component's terraform plan and apply against the same state, terraform/<repo>/main.tfstate. component_name (plan, apply, detect-drift; default '') names the component instead. base.yml exports it to bin/tf as TF_COMPONENT_NAME, only when it is set, so tf.env can still supply it. Empty, every value falls back to exactly what it is today, so existing callers are unaffected: - statefile: the git remote's repo name - drift file: github_repository_name (apply) or the repo name - Kosli flow and concurrency group: the repo name Co-Authored-By: Claude Opus 5.5 (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
2 participants
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.
tf keyed the statefile, drift file, Kosli flow and drift
concurrency group on the repository name. A repo that deploys
several components (eg cyber-dojo/web: web, creator,
dashboard) had every component's terraform plan and apply
against the same state, terraform//main.tfstate.
component_name (plan, apply, detect-drift; default '') names
the component instead. base.yml exports it to bin/tf as
TF_COMPONENT_NAME, only when it is set, so tf.env can still
supply it. Empty, every value falls back to exactly what it
is today, so existing callers are unaffected:
Co-Authored-By: Claude Opus 5.5 (1M context) noreply@anthropic.com