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

There is a way to produce a diff when running up, let me check

`pulumi up --diff` provides some detail but doesn’t make it clear why something is being replaced.

and it doesn’t work if the thing Pulumi wants to replace is protected from deletion and it’s a replace-on-change thing

ah that’s the command I was looking for, then  you need to find which part of the diff is causing the replacement. If it’s a genuine diff and the property requires the resource to be replaced, there’s no way around it unfortunately

Right, I just couldn’t tell _why_ the resource was required to be replaced.

you’re right I can’t see it in the pulumi docs, but it may be more visible in the terraform provider docs

but its in AWS CF docs if you want to check, e.g. <https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html#cfn-lambda-function-runtime>

This is for a Digitalocean Spaces bucket so the S3 docs may be helpful

this page calls out which properties will cause a replacement if you look for “_Update requires_: <https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement|Replacement>”

Hi Jack, on the registry site you can check for every property if it would trigger a recreation of the resource! 