This message was deleted.

sparse-intern-71089

09/26/2022, 12:48 PM

This message was deleted.

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.

chilly-analyst-14900

09/26/2022, 12:59 PM

pulumi stack ls | grep somestackname

as an alternative..

chilly-analyst-14900

09/26/2022, 1:01 PM

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

colossal-vr-62639

09/26/2022, 1:08 PM

Thanks @chilly-analyst-14900!

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

sparse-gold-10561

09/26/2022, 2:35 PM

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.

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.