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.

Pulumi Community

cc <@UDE2DCFT3> again :slightly_smiling_face:

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?

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

<@UDE2DCFT3> 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?

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.

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

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.