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

This question isn't specific to Pulumi; it can apply to using native Kubernetes tools as well (i.e., using `kubectl edit` to edit a Deployment to scale the replicas up, then someone re-applying the original manifest and undoing the change). The key is exactly as you suggested: you have to control how/where changes to the environment are made so there  is a single "source of truth" for the desired configuration.

You can also use `pulumi refresh` to reconcile Pulumi’s state with the state of the world if something changes out of band like that.

<@UE1LN7A22> Interesting, will check `refresh` out, thanks