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

That's the same as "Operation" when doing an `up`. I think I saw that enum in code once... let me browse..

Nope, can't find it anywhere. Do you have a specific question about Pulumi operations?

I'm configuring a key vault in azure and I noted operations showing the plan as update. While in the present case a drop and rebuild of the key vault in question would be fine, I'm interested in what else I might encounter. What the effects of the various plan decisions are to help me spread the love with my team as we adopt Pulumi.

I read about Pulumi dropping databases   for example and it would be  helpful to say if x with Azure service yy then that's destructive in the change

Update means an in-place change. Other operations are Create, Delete and Replace. Replace is used only when the provider does not support an Update, and a new resource is required.

There are other operations behind the scenes (import, query, sync maybe?), but those are the ones that can end up in the Plan (preview) or Operation (up) column.

Thanks for that, appreciate you digging that out