-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Introduce "stack move" command #888
Comments
This makes total sense.. @i4ki i noticed using tags is not fully covered in docs. Could we add examples and documentation how to use tags instead of path? This can then be used to work around the issue until |
@i4ki (?) pointed out that tags can not take a variable (for now). And, dir specification made a lot of sense to me. |
@az-z @mariux indeed the documentation is not good. The Tag Filter docs don't mention how it should be used in the I'm gonna improve the docs ASAP. Meanwhile, have a look in the example below:
The config above declares a stack that must run after the stacks tagged with The syntax after the |
We improved the documentation of using |
Hi @az-z did using tags solve your initial issue? If so, would it be okay to close this request? |
Closing now, please re-open when this did not solve your poblem. |
@mariux , some background. each environment has "globals.tm" that defines and assigns variables for this particular environment: the "PROD" is fully functional code - it was deployed yesterday with TM's help. The code does not use TM's tags. e.g:
each stack has `stack.tm.hcl that generates terraform.tfvars, e.g:
as you can see there are 3 types of dependencies on the stack level:
I hope, that with this information, the following errors should be less cryptic:
I truncated the full paths in the message above. Issues:
Next, i'll add tags and repeat the clone operation. I'll report the results shortly. P.S. |
the changes i made:
in d9/prod/cicd stack.tm:
|
Thanks for reporting this @az-z, I just reopened the issue. Let me look at this with the team tomorrow and get back to you! |
Is your feature request related to a problem? Please describe.
to manage dependencies efficiently, it may be useful to introduce a "stack move" command.
Describe the solution you'd like
tm stack move <path to source stack| uniquely identifiable tags> <path to destination>
as part of the move:
The "move" can also serve as a "rename" with the same functionality.
Describe alternatives you've considered
potential alternative
The text was updated successfully, but these errors were encountered: