you could also use the protect true on those things once you

Question

you could also use the protect true on those things once you re happy with them <https www pulumi com docs intro concepts resources protect>

fresh-summer-65887 · Answer

Yeah considered that too But it s easy to just remove it though that might not be a refactoring but more deliberate altering

worried-knife-31967 · Answer

I m not sure if you re aware I wasn t it s not the same as a terraform `prevent destroy` you have to use the CLI to remove it making it quite useful when combined with users not have access to the CLI

worried-knife-31967 · Answer

i e once you ve added it it s there you can t just remove the code and it will destroy it

worried-knife-31967 · Answer

In Azure I ve coupled that with a lock on the resource for extra protection

fresh-summer-65887 · Answer

This also works in CI scenarios

fresh-summer-65887 · Answer

interesting

fresh-summer-65887 · Answer

Thanks for info slightly smiling face

worried-knife-31967 · Answer

I ve hit it in CI which is where I noticed it but I was using the Azure Blob backend I m not sure if that s a nuance of the Azure blob backend though

worried-knife-31967 · Answer

<https www pulumi com docs reference cli pulumi state unprotect > When you look at the CLI though it does seem to suggest that it s the only way to remove the protect bit from the state