05/18/2020, 2:25 PM
In an automation setup, I am trying to automate the following sequence with local state backend:
Copy code
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.