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

&gt; Could it potentially be a problem where a github action times out or something and appears to have successfully completed, but the state was not completely transferred to the pulumi service?
That's possible but the state will record that it started the operation, and warn you about partial operatings if that happens.
Can you `pulumi refresh` the stack to see if pulumi thinks it's out of sync with AWS?

Not easily, no. I can add a manually trigger to the github action and see, but for now I ended up committing a change that removed the resource, and recreated it again, and it appears to add or remove actions within this AWS policy just fine now. If it happens again, I will do a refresh and perhaps create a bug report / reply in this thread?

Sure, I will create one if it happens again and try to reproduce it if possible

I just did not have time for that now, and had to move on without waiting.

Not entirely sure how I should go about reporting this as a bug, because I don’t really understand how I end up in this state. It appears to occur when trying to change IAM policies in AWS after a failed `pulumi up`has occurred before hand.

Just post as much info as possible, what happened, the output from the `up` that failed, etc. If we need more we can reply to the ticket.