I have a TaskDefinition with 5 containers in it. On each

update

Pulumi is basically noticing a difference in the order of the containers in the list and recreating the TaskDef although the resulting TaskDef is actually unchanged. I've had this before in Terraform with Env Vars needing to be sorted alphabetically to avoid the recereation. Reordering the list to match so far hasn't worked, it still notes a difference each time. I do have

refresh: always

turned on, and would like to keep it. Has anyone else seen/solved this issue?

Oof. I suspect that this is b/c of the use of a Go map behind the scenes (iterating the keys of a Go map is non-determinative, much to the chagrin of many a developer).

Yeah, seems like we should be using an ordered data structure. What is strange to me is that I've not run into this until today

Is there's an issue in the underlying TF provider, then that would need to be fixed first. If TF does not exhibit the same behavior, then it's a Pulumi bug. File an issue in pulumi/pulumi-aws if one does not yet exist and someone will look at it in the next couple of business days.

I've noticed this behaviour too. Thought it was something I was doing. Sounds bad but I hope it's a Pulumi bug because it'll actually get fixed. Pull-requests on the TF provider are often left to gather dust tumble weed

Unfortunately, there's not a lot Pulumi can do to influence HashiCorp to accept the PR. (We have more influence on other bridged providers, particularly when they are our partners.)