I have two stacks, stackA and stackB. (code below)
StackB references a stack output from stackA and stackB uses it for a resource property.
Initial updates work as expected - stackB consumes the stack output and uses it as expected in creating it’s resource.
But if I change stackA so the output has a different value and run update on stackA and then update on stackB, stackB does not identify any changes needed.
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
What happened?
I have two stacks, stackA and stackB. (code below) StackB references a stack output from stackA and stackB uses it for a resource property. Initial updates work as expected - stackB consumes the stack output and uses it as expected in creating it’s resource. But if I change stackA so the output has a different value and run update on stackA and then update on stackB, stackB does not identify any changes needed.
Stack A Code:
Stack B Code:
Expected Behavior
StackB's stack reference to stackA should trigger an update in stackB when stackA's output is changed.
Steps to reproduce
Output of
pulumi about
CLI
Version 3.73.0 Go Version go1.20.5 Go Compiler gc
Plugins NAME VERSION pulumi unknown random unknown yaml unknown
Host
OS darwin Version 13.4.1 Arch x86_64
This project is written in yaml
TYPE URN pulumi:pulumi:Stack urn:pulumi:dev::stackB::pulumi:pulumi:Stack::stackB-dev pulumi:providers:pulumi urn:pulumi:dev::stackB::pulumi:providers:pulumi::default pulumi:pulumi:StackReference urn:pulumi:dev::stackB::pulumi:pulumi:StackReference::stack-a-reference pulumi:providers:random urn:pulumi:dev::stackB::pulumi:providers:random::default random:index/randomPet:RandomPet urn:pulumi:dev::stackB::random:index/randomPet:RandomPet::petnameB
Found no pending operations associated with dev
Backend
Name pulumi.com
No dependencies found
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).