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

In an automation setup, I am trying to automate the following sequence with local state backend:
```pulumi login file:///var/pulumi/state
pulumi stack init production --secrets-provider=passphrase
pulumi up --diff --yes```
However, in my script, is there a way to have `pulumi stack init` not error on the second and subsequent runs? I could silence it with a shell construct, but then I could possibly mask a possible error on the first run.