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

After updating awsx to `0.18.1`, Pulumi updates my Fargate task definitions which forces all my `awsx.ecs.FargateService` to redeploy. Is this a known regression?

cc <@UB9JVTW07>

<@UCZ0LS7NZ> What is the update you are seeing?

If I look in the Pulumi UI console, all that changed were the task definition versions.  For example:
```
+- aws:ecs/taskDefinition:TaskDefinition (create-replacement)
    [id=modelExecutor-09a16bb3]
    [urn=urn:pulumi:app-dev::services::awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::modelExecutor]
    arn                    : "arn:aws:ecs:us-west-2:734247230719:task-definition/modelExecutor-09a16bb3:64" =&gt; "arn:aws:ecs:us-west-2:734247230719:task-definition/modelExecutor-09a16bb3:65"
    revision               : 64 =&gt; 65
```

Is there more to that?  Is there a plain `replacemnent` row that shows the full set of proposed changes/replacements?