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
Is your feature request related to a problem? Please describe.
Not exactly a problem, but it would be awesome to streamline the workflow. Making stack creation even smoother would enhance the overall experience when managing multi-region and multi-environment deployments in large teams.
Describe the solution you'd like
It would be cool if terramate create could support glob patterns in the path attribute. For example:
terramate create stacks/prod/network/{eu-north-1,eu-central-1}/ec2
or
terramate create live/*/network/eu-north-1/ec2
Describe alternatives you've considered
Creating stacks one at a time for each region and environment commando style, or considering scripting the creation, using Makefiles, or other similar tools.
The text was updated successfully, but these errors were encountered:
For both options you proposed, the only missing functionality is allowing multiple stack paths in the terramate create.
The problem is that --id, --name and --description are meant to be set to an individual stack, so it's meaningless if providing multiple paths.
Maybe only if we error if those flags are provided together with multiple stack paths?
Is your feature request related to a problem? Please describe.
Not exactly a problem, but it would be awesome to streamline the workflow. Making stack creation even smoother would enhance the overall experience when managing multi-region and multi-environment deployments in large teams.
Describe the solution you'd like
It would be cool if terramate create could support glob patterns in the path attribute. For example:
Describe alternatives you've considered
Creating stacks one at a time for each region and environment commando style, or considering scripting the creation, using Makefiles, or other similar tools.
The text was updated successfully, but these errors were encountered: