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

This is another issue that we've fixed that I believe has not made it into a release.

In the meantime, you should be able to run `pulumi refresh` on the downstream stack

so i tried running refresh and its still not detecting the change, how can i tell if it has?

oooh, so the stack has an error (due to this issue) that is preventing the refresh from happening

Is there a way to tell it to ignore errors?

There is not. What is the error that you're seeing?

Type                             Name                       Plan        Info
     pulumi:pulumi:Stack              compound-api-compound-api
 ~   ├─ pulumi:pulumi:StackReference  databases                  update      [diff: ~outputs]
     ├─ pulumi:pulumi:StackReference  infrastructure
     ├─ pulumi:providers:kubernetes   kube
     ├─ pulumi:pulumi:StackReference  identity
     ├─ kubernetes:core:Service       api
 ~   └─ kubernetes:apps:Deployment    api                        refresh     1 error

That's interesting--it's not telling you what the error is?

It does, its some random error about liveness

I solved it by destroying the stack and recreating

Seems like we shouldn't fail the refresh due to that error, though.

<https://github.com/pulumi/pulumi/issues/2352>