This message was deleted.
# general
s
This message was deleted.
😞 1
🤔 1
b
this sounds scary, can you share more of the diff/output? feel free to DM me
are you using the OSS backends? did you run preview before you ran
pulumi up
?
f
Using the Azure blob backend.
The sadness of the whole story is I was just about to add protect to all of the important resources. I was just cleaning something up.
Edited title, as I'm sure some part of my system messed up here, I just don't know where.
b
I would love to see the diff from your CI to debug this, usually when I see this it’s because the connection to the object store isn’t corrrct
f
yeah, will definitely send it, just trying to restore everything first, it's been one of those days
@billowy-army-68599: Finally got everything in a good place, ended up being an out of order job against an old commit that retried AFTER I migrated everything over, blowing some pieces of imported infrastructure away. ... I didn't have resource locks or `protect`s on this infra yet as it was a dev tier under development. Luckily we had backups for everything, it just cost me a day of pain after blowing things away.
b
ah sorry to hear that. you might want to turn on state locking too:
Copy code
PULUMI_SELF_MANAGED_STATE_LOCKING=1
🙌 1