This message was deleted.

sparse-intern-71089

08/26/2022, 5:18 PM

This message was deleted.

strong-helmet-83704

08/26/2022, 5:25 PM

My best guess is… because i added the

retain_on_delete=True

flag to code AFTER my stack was already created, Pulumi has not had the opportunity to add this option to the stack/state for that resource…?

strong-helmet-83704

08/26/2022, 6:39 PM

I think if i perform a “pulumi up” after adding the option… it works as expected. But it’s not reported as an update to the stack/state… If I perform a destroy it will not read the the option from code.

square-ability-48831

08/26/2022, 6:56 PM

yeah if i'm not mistaken you need to do a

pulumi up

to get the

retain_on_delete

to pulumi's state store - the

pulumi up

will not report any changes, but it will add the

retain_on_delete

attrib to the state file - if you're using the pulumi hosted state, check

pulumi console

before and after the no-op

up

strong-helmet-83704

08/26/2022, 7:01 PM

This fits with my understanding! Why is the state change not reported during the “up”?

square-ability-48831

08/26/2022, 7:02 PM

because there's no change to AWS - just the state file. would be nice to see those reported too

✅ 1

🙌 1

👍 1

strong-helmet-83704

08/26/2022, 7:03 PM

I think any change being made to any state would be desirable to see…

strong-helmet-83704

08/26/2022, 7:28 PM

does a refresh do this?

2 Views

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.