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.

Pulumi Community

I'm reasonably certain this would be expected behavior for `pulumi destroy`, but I didn't think `pulumi up` worked the same way. Making some internal inquiries now.

Thank you, Just putting this info here if needed

pulumi v.3.99.0, pulumi-aws=6.15.0

OK, this is expected behavior. You'll need to run `pulumi refresh` first, or use `pulumi up --refresh` to address this sort of situation.

There's also a project configuration option that allows you to set this behavior to happen automatically. See here: <https://www.pulumi.com/docs/concepts/projects/project-file/#example-project-file-with-all-possible-attributes>