When issuing `pulumi stack init` on an existing stack is the

Question

When issuing `pulumi stack init` on an existing stack is there a way to ignore the fact that it already exists Use case Looking at a way to create stacks on the fly without needing to do a lookup of sorts before issuing an `init`

chilly-analyst-14900 · Answer

+1 I ended up doing the init and swallowing the error I see the github actions amp the automation API has support for upsert but not the CLI

chilly-analyst-14900 · Answer

`pulumi stack ls | grep somestackname` as an alternative

chilly-analyst-14900 · Answer

Using the Pulumi CLI in a GH action step ``` name Create new pr stack run | pulumi stack init non interactive logtostderr $ env STACK NAME working directory infra env PULUMI ACCESS TOKEN $ secrets PULUMI ACCESS TOKEN continue on error true init fails if exists```

colossal-vr-62639 · Answer

Thanks < chilly analyst 14900>

sparse-gold-10561 · Answer

It would be nice if `pulumi stack select` had a flag like auto create if it didn t exist

sparse-gold-10561 · Answer

because then you wouldn t have to worry about initializing it as the stack select would initialize it and if it already exists it would just select it