Hi, I'm managing our infra at my company and we just started using pulumi (python) with AWS infra. I've seen a lot of posts related to provider changes triggering existing infra to be replaces, which is pretty thorny imo. I initially thought that upgrading

pulumi_aws

would be the main reason this would occur, but even on the same

pulumi_aws==6.54.0

, I still see pulumi trying to replace my infrastructure. How can I prevent this? Here is a quick summary after running preview

pulumi:pulumi:Stack ecs-task-def-dev running read pulumi:pulumi:StackReference dev
@ Previewing update....
    pulumi:pulumi:Stack ecs-task-def-dev running read pulumi:pulumi:StackReference dev
@ Previewing update.....
 ++ aws:ecs:TaskDefinition <redacted> create replacement [diff: ~containerDefinitions,provider]
 +- aws:ecs:TaskDefinition <redacted> replace [diff: ~containerDefinitions,provider]
 ++ aws:ecs:Service <redacted> create replacement [diff: ~provider,taskDefinition]
 +- aws:ecs:Service <redacted> replace [diff: ~provider,taskDefinition]
 ++ aws:appautoscaling:Target <redacted> create replacement [diff: ~provider]
 +- aws:appautoscaling:Target <redacted> replace [diff: ~provider]
 ++ aws:appautoscaling:Policy <redacted> create replacement [diff: ~provider]
 +- aws:appautoscaling:Policy <redacted> replace [diff: ~provider]
@ Previewing update....
 -- aws:appautoscaling:Policy <redacted> delete original [diff: ~provider]
 -- aws:appautoscaling:Target <redacted> delete original [diff: ~provider]
 -- aws:ecs:Service redacted> delete original [diff: ~provider,taskDefinition]
 -- aws:ecs:TaskDefinition <redacted> delete original [diff: ~containerDefinitions,provider]
    pulumi:pulumi:Stack <redacted> 
Resources:
    +-4 to replace
    1 unchanged

I'm looking for a solution to this as well. It's trying to replace the entire AWS EKS cluster because of a provider update. That is absolutely insane. I can use the current/older provider, but it feels like I'd be stuck on an old version forever until/unless I want to replace the entire cluster (which I don't want to do, probably ever)

Does your resources was imported? We also start seeing this issue on some resources starting at version

6.51.1

My resources were all imported

this issue is absolutely infuriating imo, and this comes up with every provider upgrade.