gifted-island-55702
12/19/2018, 3:09 PM[object ..]
instead of the actual project id string). This was “consumed” in my another stack via a stack reference and getOutput
. 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?white-balloon-205
white-balloon-205
gifted-island-55702
12/19/2018, 10:56 PMpulumi update
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)white-balloon-205
white-balloon-205
gifted-island-55702
12/19/2018, 11:05 PMpulumi update
. 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 pulumi update
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 configmapgifted-island-55702
12/19/2018, 11:06 PMwhite-balloon-205
StackReference
? And just a case where you are adding a new export instead of changing an existing export?gifted-island-55702
12/19/2018, 11:14 PMexport const testOutput = 'abc'
) and then consume it in stack 2 with new StackReference('stack1').getOutput('testOutput')
and put it as another entry in k8s config map