gifted-island-5570212/19/2018, 3:09 PM
instead of the actual project id string). This was “consumed” in my another stack via a stack reference and
. The issue was that after I have fixed the kubeconfig output in my first stack, the one that was consuming it hasn’t detect any changes and I couldn’t fix the issue reported by k8s provider due to invalid yaml config. Is there a document describing when outputs are being updated in the consuming stacks?
gifted-island-5570212/19/2018, 10:56 PM
in the second stack that uses output from the first stack but it didn’t find any updates in the output value (was still using the old and incorrect value)
gifted-island-5570212/19/2018, 11:05 PM
. I could see the output added in app.pulumi.com console
- I have added a usage of this output in stack 2 (another key in k8s configmap) and I run
in stack 2 but the preview shows there are no changes to be applied and when I run this update the new key is not added to the configmap
? And just a case where you are adding a new export instead of changing an existing export?
gifted-island-5570212/19/2018, 11:14 PM
) and then consume it in stack 2 with
export const testOutput = 'abc'
and put it as another entry in k8s config map