powerful-football-81694
01/17/2020, 1:22 PMcommand: stack
and options: init $(StackName)
in the YAML.
However, the Pulumi@1
task has a mandatory stack
parameter, and the task always tries to select that stack the first thing it does, before it proceeds to execute the actual command, which of course results in an error because the stack does not yet exist.tall-librarian-49374
01/17/2020, 1:44 PMclever-sunset-76585
01/17/2020, 2:59 PMpowerful-football-81694
01/17/2020, 3:44 PMclever-sunset-76585
01/17/2020, 4:01 PMpowerful-football-81694
01/17/2020, 4:21 PMstack
parameter remained required, and you added a stack init
command to the task, that uses this parameter for the stack init, but does not try to do the select first?stack init
command could then also “swallow” the error that occurs if the stack already exists. Something we would otherwise need to do in the pipeline.clever-sunset-76585
01/17/2020, 5:09 PMpulumi/pulumi
.
I implemented a similar thing for our Octopus Deploy Step Template too. It allows you to create a stack miniature-chef-87843
01/20/2020, 8:34 PM