This message was deleted.

sparse-intern-71089

02/08/2019, 9:44 PM

This message was deleted.

white-balloon-205

02/08/2019, 11:37 PM

We recently changed this to use a different word to avoid the confusion - Pulumi will not actually delete the resource from the cloud provider if it was read in with

.get

. Re: marking as not delete, there is an option in the ResourceOptions for any resource that can say

protected: true

which will prevent any attempt to delete the resource until that property is first removed in a separate update.

brave-salesmen-42327

02/16/2019, 4:02 PM

Hello, Just started using Pulumi. I am reading in a set of global/shared resources using .get(). When i execute a destroy command it still labels them as to be deleted. also the resource option { protected: true } does not appear correct. It seems like its supposed to be { protect: true }. None of those prevent it from being listed for deletion on a destroy command though.

brave-salesmen-42327

02/16/2019, 4:04 PM

Code that results in resources still being flagged for delete, or argument errors

brave-salesmen-42327

02/16/2019, 4:05 PM

Flagged for delete, even though .get or {protect:true} was used.

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.