You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the generate command only on the 1st stack using the --tags option
terramate generate --tags aws
Expected behavior
I would expect the code generation to be applied only to the 1st stack and not to all. The help page of the terramate generate commands indicates that it supports the --tags=TAGS option to filter stacks by tags.
Thanks for answering this @bart-braidwell, I actually only saw this now. In addition to condition you can also use stack_filter such as repository_paths and project_paths.
In addition to that, the code generation always run on the entire repository / Terramate project to prevent inconsistencies as there are plenty of factors that impact generated files such as globals, locals, etc. Partial code generation is not a good idea.
Describe the bug
To Reproduce
Create 2 stacks, only one with a tag
Add the code generate file
stacks/main.tm.hcl
with the contentRun the generate command only on the 1st stack using the
--tags
optionExpected behavior
I would expect the code generation to be applied only to the 1st stack and not to all. The help page of the
terramate generate
commands indicates that it supports the--tags=TAGS
option to filter stacks by tags.Log Output
The code generation runs for all stacks
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: