Maybe I'm missing something obvious, but if I have a resource that starts a Docker container, then a resource that takes an action on that Docker container (in my case, starting Consul and then connecting to Consul), and then if I kill the Consul container, refresh doesn't work. I think I need to refresh to let Pulumi know that the container is down (since just running up doesn't restart it). But the refresh fails because my second resource attempts to connect to Consul (which is down) and fails. Thus, I can't refresh and up doesn't bring me back into compliance.

maybe the

ignoreChanges

opt can help you