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

Hey :wave:
Facing an issue where Pulumi forces a replacement of Docker images on each new deployment without any changes done to the deployment code/dockerfile.
Pulumi output just shows `[diff: ~provider]`  - we're using `awsx.ecr.Image`.
The issue started popping up ~last week. No changes have done to this part of our codebase recently, causing us to question whether the issue could be on Pulumi side :eyes:

due to the `provider` difference, the deployment essentially is in a loop, where on:
• deployment one - changes provider, which causes the image to not even be visible in AWS console
• deployment two - fully builds and deploys the image again

Hmmm... That sounds quite unhelpful. I use the Docker provider myself, but I'm only using tagged images from Docker Hub, not my own Dockerfile. Hang tight, I'll find someone to ask.

<@U099VGDJCUB> (or mby now <@U09A1B61F6W>), any updates on who to ask?

Hey Heido, thanks for reaaching out again. Have you cut us a github issue with the problem? I think that might be the next step. If you can make a small test pulumi program that reproduces this behavior I can start to look into it.