This message was deleted.

sparse-intern-71089

01/17/2020, 1:22 PM

This message was deleted.

tall-librarian-49374

01/17/2020, 1:44 PM

cc @clever-sunset-76585 again 🙂

clever-sunset-76585

01/17/2020, 2:59 PM

Ah yes. I thought about making the stack input optional for this very reason, but didn't because well it hadn't come up till now. Mind opening an issue?

powerful-football-81694

01/17/2020, 3:44 PM

@clever-sunset-76585 Sure - what’s the repo?

clever-sunset-76585

01/17/2020, 4:01 PM

It's https://github.com/pulumi/pulumi-az-pipelines-task

powerful-football-81694

01/17/2020, 4:21 PM

@clever-sunset-76585 wouldn’t it make more sense if the

stack

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?

powerful-football-81694

01/17/2020, 4:22 PM

Such a

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.

powerful-football-81694

01/17/2020, 4:25 PM

https://github.com/pulumi/pulumi-az-pipelines-task/issues/34

clever-sunset-76585

01/17/2020, 5:09 PM

Yep that’s what I am thinking too. There is a need for an “ephemeral” stack capability in Pulumi itself and I think there is an issue open in

pulumi/pulumi

. I implemented a similar thing for our Octopus Deploy Step Template too. It allows you to create a stack of if it does not exist.

miniature-chef-87843

01/20/2020, 8:34 PM

+1 for this

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.