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.
Add the ability to run against a stack by name or id
Describe the solution you'd like
In a CI in our testing scenario, we are deploying the stable version first before deploying the new change, simulating an upgrade to the platform before production. the problem is, if the stack gets moved in the filesystem in the head version, even if terramate detects the changed stack in the new version, I could not know what is the corresponding location of the stack in the stable version, combined with #723 one could use the combination of terramate list --changed --json and terramate run -id stack_id to run the stacks in workflow matrix
prepare_contaxt:
name: Contextruns-on: ubuntu-latestoutputs:
changed_stacks=${{steps.get_stacks.outputs.stacks}}steps:
- id: get_stacksrun: echo "stacks=$(terramate list --changed --json)" > $GITHUB_OUTPUTtest_deploy:
name: Deploy / Testruns-on: ubuntu-latestenvironment: Stagingneeds: prepare_contextstrategy:
matrix:
stack: ${{ fromJson(needs.prepare_context.outputs.changed_stacks) }}steps:
# ...
- name: deploy stablerun: | terramate list --changed | grep ${{ stack.id }} && # run only if it exists in stable terramate run -id ${{ stack.id }} -- terraform apply
The case of terramate run --name is just a convenient way to run by stacks name rather than remembering tags. for now to run by name we had to duplicate the name in the tags !
Describe alternatives you've considered
Too long :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Add the ability to run against a stack by
name
orid
Describe the solution you'd like
In a CI in our testing scenario, we are deploying the stable version first before deploying the new change, simulating an upgrade to the platform before production. the problem is, if the stack gets moved in the filesystem in the head version, even if terramate detects the changed stack in the new version, I could not know what is the corresponding location of the stack in the stable version, combined with #723 one could use the combination of
terramate list --changed --json
andterramate run -id stack_id
to run the stacks in workflow matrixThe case of
terramate run --name
is just a convenient way to run by stacks name rather than remembering tags. for now to run by name we had to duplicate the name in the tags !Describe alternatives you've considered
Too long :)
The text was updated successfully, but these errors were encountered: