I’m making a small change to a service discovery namespace (removing description) and hitting an issue where pulumi wants to replace it but AWS says no you cannot as there are ECS services relying on it. 1. description should not really need a replace IMHO but this may be an AWS issue 2. do we expect pulumi to manage this type of situation OR is it expected that I need to go through a deprecation approach where I add a new resource, switch services to that in one pulumi run then remove the old resource in another pulumi run? I don’t really mind if 2 is the case but wanted to ask in case not and I’ve found a bug OR if it is the case so I can document the gotcha for my team.