https://pulumi.com logo
#general
Title
# general
h

helpful-advantage-49286

01/11/2019, 10:41 PM
what am I missing?
m

microscopic-florist-22719

01/11/2019, 10:42 PM
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
and that should pick up the changes
h

helpful-advantage-49286

01/11/2019, 10:43 PM
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?
m

microscopic-florist-22719

01/11/2019, 10:45 PM
There is not. What is the error that you're seeing?
h

helpful-advantage-49286

01/11/2019, 10:45 PM
Type Name Plan Info pulumipulumiStack compound-api-compound-api ~ ├─ pulumipulumiStackReference databases update [diff: ~outputs] ├─ pulumipulumiStackReference infrastructure ├─ pulumiproviderskubernetes kube ├─ pulumipulumiStackReference identity ├─ kubernetescoreService api ~ └─ kubernetesappsDeployment api refresh 1 error
m

microscopic-florist-22719

01/11/2019, 10:46 PM
That's interesting--it's not telling you what the error is?
h

helpful-advantage-49286

01/11/2019, 10:47 PM
It does, its some random error about liveness
because the deployment cant come up
m

microscopic-florist-22719

01/11/2019, 10:47 PM
Ah, got it
cc @creamy-potato-29402
h

helpful-advantage-49286

01/11/2019, 10:47 PM
I solved it by destroying the stack and recreating
m

microscopic-florist-22719

01/11/2019, 10:47 PM
Good to know you're unblocked.
Seems like we shouldn't fail the refresh due to that error, though.
I'll file an issue
h

helpful-advantage-49286

01/11/2019, 10:50 PM
Thanks!
c

creamy-potato-29402

01/11/2019, 10:51 PM
hmmm