https://pulumi.com logo
Powered by
#general
Title
# general
c

colossal-vr-62639

09/26/2022, 12:48 PM
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
.
c

chilly-analyst-14900

09/26/2022, 12:59 PM
+1. I ended up doing the init and swallowing the error. I see the github actions (& the automation API) has support for upsert, but not the CLI.
pulumi stack ls | grep somestackname
as an alternative..
Using the Pulumi CLI in a GH action step:
Copy code
- 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
👍 1
c

colossal-vr-62639

09/26/2022, 1:08 PM
Thanks @chilly-analyst-14900!
s

sparse-gold-10561

09/26/2022, 2:34 PM
It would be nice if 
pulumi stack select
had a flag like --auto-create if it didn't exist
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.
Powered by