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

That’s potentially a bug. Could you file an issue, either in pulumi-aws for the classic provider or pulumi-aws-native for the native provider? Ideally with a complete program to reproduce, but we can figure it out if that’s difficult to extract. Thanks!

<@U038021B1CJ> I realized that I never opened this issue… here it is: <https://github.com/pulumi/pulumi-aws/issues/2491>

Still seems to be happening on my end with latest versions of Pulumi

Does the use of `awsx` raise any flags for you?

And is it possible there’s a similar non-idempotent issue with `aws:cloudformation:Stack`?

`awsx` seems unrelated at first glance. We actually have a small number of similar issues open where Pulumi thinks unchanged resources have changed. That suggests an underlying bug. I’m compiling these at the moment so we can track this down. Sorry for the trouble!

Should I open an issue for the `aws:cloudformation:Stack` one as well?

Hmm, yes I think that would be good to have a full picture, if you don’t mind

<https://github.com/pulumi/pulumi-aws/issues/2492>