This message was deleted.
# automation-apis
sparse-intern-71089
07/13/2021, 5:57 PMThis message was deleted.
r
red-match-15116
07/13/2021, 6:20 PMI guess you could loop over ASG creation, pass in an array of names as a config value and that would let you do something like this.
b
bright-dawn-60437
07/13/2021, 6:21 PMYeah, but the names will be
[“name1”]
in first run
and [“name2"] in second run.
Which I need to handle as [“name1”, “name2"]
bright-dawn-60437
07/13/2021, 6:22 PMGuess a better question is - is it possible to do what I want to do as multiple stack, but be able to list all the stack that I create this way?
bright-dawn-60437
07/13/2021, 6:22 PMOne option seems to be tags, is it possible to list stacks by tags?
r
red-match-15116
07/13/2021, 6:22 PMYes, my suggestion would be to always create a new stack.
red-match-15116
07/13/2021, 6:23 PMYou can keep all such stacks in one specific project. Or you could name the stacks in a way that has this information.
asg-name1asg-name2red-match-15116
07/13/2021, 6:24 PMListing stacks by tag is not possible currently via automation api
b
bright-dawn-60437
07/13/2021, 6:25 PMCould you point me at how I can get all stack in a project? Last I checked (might have done it wrongly), it needed both stack name and project name. Using the python sdk
r
red-match-15116
07/13/2021, 6:26 PMb
bright-dawn-60437
07/13/2021, 6:27 PMGot it, thanks a lot. Will try this way!
👍🏽 1