Detect ENV vars in YAML stack config and set them for command execution. Make workspace_key_prefix
config DRY
#77
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.
what
workspace_key_prefix
config DRYvarfiles
after each commandwhy
backend
section hasworkspace_key_prefix
fors3
backend type. If it does not, use the component name instead. It also propagates toremote_state_backend
section ofs3
type. This will allow to have components catalog files DRY without repeating the same config (which now can be generated automatically by the component names). Components folders are supported and taken into account in the generatedworkspace_key_prefix
. This can be overridden as before per component.This config
is now the same as this
and produces the same result (confirmed by the updated tests)
varfiles
after each command - sometimes it's useful to be able to runatmos terraform plan
and then use the generatedvarfile
andplanfile
in other terraform commands. Thevarfile
andplanfile
can be deleted by now supported commandtmos terraform clean <component> -s <stack>