Hi all 👋 I was wondering if someone has an idea for a solution for the following scenario: • I have the following dependency tree:

FileArchive <-- azure.Blob <-- k8s.Deployment <-- k8s.Service

• When a change occurs to the hash of the

FileArchive

, the

Blob

is marked as

replace

, and that leads to a cascading replace on the K8s

Deployment

and

Service

• Is there a way to mark the changes (inherited) changes in the Deployment/Service as non-replacing changes (it's a safe-update), or a way to force Pulumi to make an update (instead of

replace

) for the

Blob

? 🤔 • The scenario above causes some downtime issues, since changing the blob changes the Deployment spec, and that leads to downtime, because sometimes Pulumi just replaces the original K8s

Deployment

in a non-graceful way 😞 (we see that it deletes and only then creates a new Deployment) Thanks 🙂

just noticed the same but with

Docker.Image

. It first removes the deployment, then waits a minute while the image is being built, and only then creates a new deployment.

Yeah I feel it's a very similar issue. Some resource cascaded their "replace" state into their dependencies, even when it does not make sense (for things like Deployment)

Well, I have read a lot of issues and it seems there is no way to control the update vs replace behavior yet. Though there is a

replaceOnChanges

option, looks like it is the opposite of what we want. The only way to deal with accidental deletes is the

protect

resource option, which throws an error if some state diff results in replacement. With this, we could at least figure out exactly which changes are not updatable. Also there are fields that always trigger the replacement, in case of Deployment check the docs and search on the page for:

Cannot be updated

.

Yeah 😞