This message was deleted.
# general
s
This message was deleted.
b
FWIW, this happens with both Pulumi 3.4.0 and 3.22.1 (the latest), no difference.
Updates are currently no ops unless there is a replacement
b
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?
s
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
b
I see. Definitely not what I expected, probably worth a quick doc note in the README 🙂
And if I have it correct, there’s no way to do an update today, correct? It’ll always be a delete/create cycle.
s
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.
b
FWIW, I opened an issue on my first thing, which I’ll update with the discussion here.
I’m adding a comment with my findings/thoughts too (just saw yours too)
👍 1
Done, thank you.