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 team. I've got a problem when I update a task definition for an ECS service in AWS, Pulumi up indicates changes, which I make however when I run pulumi up again (with no code changes) it again indicates an update to perform. Does anyone know how to diagnose this? Ive compared the AWS json task definitions of before and after and they are exactly the same. :disappointed:

Found the problem <@UCWG26BH7> - I was adding a fluentbit container on my task definition for datadog log parsing from ECS Fargate. For some reason, pulumi is adding a ‘user: 0’ into the container definition which wasn’t in my code. It also did not show on pulumi refresh either so every time it was adding this user ID but it was never tracked anywhere 