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

there's some interesting recalculation going on with the `containerDefinitions` property of a Fargate TaskDefinition. I've got updates on every `pulumi up`, even when I don't change anything about the container. I'm trying to fill in the deltas between the configurations that I see when doing `pulumi up --diff` to see if I can get the states to ever sync up and not require re-pushing, but there are definitely some default values that are represented in the 'deployed model' that aren't represented in the 'about to deploy' model

I did manage to get the changesets to line up, it seems to be a few missing properties in the calculated changes that cause it to get out of sync. it looks like the `healthcheck` property doesn't register the defaults correctly?
`healthcheck.{interval, retries, timeout}` must all be specified exactly or else the container definition is replaced every time.  Anyone else seeing this?

<https://github.com/pulumi/pulumi-aws/issues/847> for reference for anyone