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

FWIW, this happens with both Pulumi 3.4.0 and 3.22.1 (the latest), no difference.

<https://github.com/pulumi/pulumi-command/blob/master/provider/pkg/provider/provider.go#L278>

Updates are currently no ops unless there is a replacement

What constitutes a replace in this case? It seems like just updates to inputs (e.g. environment or other dependencies) won’t have any impact, so it won’t get replaced?

As defined by default just changing the name etc. would trigger a replace I believe. You could trigger the replace by adding a `replaceOnChanges: ["environment"]`  option on the resource

I see. Definitely not what I expected, probably worth a quick doc note in the README :slightly_smiling_face:

And if I have it correct, there’s no way to do an update today, correct? It’ll always be a delete/create cycle.

That is my understanding. Perhaps we need an update hook as well? Feel free to open a feature request on the repo to start that conversation if you feel like you have a good use case.

FWIW, I opened an issue on my first thing, which I’ll update with the discussion here.

<https://github.com/pulumi/pulumi-command/issues/37>

I’m adding a comment with my findings/thoughts too (just saw yours too)