Yes I'm following that, I think this is extremely important, more than ever with kubernetes resources.
There are a lot of cases where you need to edit a resource that was not created by pulumi (default storage class, eks addons and so on), there are some solutions to manage this but at the moment none of them is doable:
• Import the resource and allow to have different attributes on the same run of the import
• Create a resource with the same id and allow to override the original one
• Have a sort of a patch resource
At the moment I'm writing a lot of dynamic resources that do kubectl apply under the hood