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

What would you want to be able to do here?  (Or how would you expect refresh to work?)

I am typing up a GitHub issue...what I would like to be able to do is a force an update to resource property by name.

so if I have a kubeconfig i need updated from a infra-cluster microstack as example, and i need all my other microstacks to update their stack with the new one from that one, I can run a command to easily do that...

the issue is that when the nodes get replaced, the deployments go away...so when you run an update it has incorrect state...and if you try to refresh to correct it, it doesn't have the ability to connect to the new node

its not a super common scenario...but if you modify something on your cluster like say update the release channel and you use microstack you will be in this situation...

<https://github.com/pulumi/pulumi-kubernetes/issues/887>