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

Hi all - any tips on debugging an AWS resource that is always marked as updated? I assume it's something relating to the order of elements in some of the arrays I'm passing as `pulumi refresh` shows no differences and yet a `pulumi preview` will show each of my AWS Cognito clients as being updated.

I'm guessing it could be an upstream issue but is there a way of diagnosing?

Does it say which attribute is causing pulumi to think that the state is out of sync? If so, you can mark that attribute as "ignored" in the resource definition.

Yeah - that's what I've tried - but I've now ignored all of the ones I'm setting to no avail :disappointed:

There must be a diagnostics level which lists the changes... but how to find it?