-
Notifications
You must be signed in to change notification settings - Fork 878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack Reference in Open Source #752
Comments
StackReference is available for open source users. However, the ability to use different secrets providers across stacks isn't possible today given the way secrets providers work and is tracked in pulumi/pulumi#4665 |
Thank you for the response. |
Yes -- if you want the StackReference to work, they need to use the same secrets provider. Note that in the open source, you can also use other secrets provider that aren't just the passphrase: https://www.pulumi.com/docs/intro/concepts/config/#available-encryption-providers |
But using the same secrets provider doesn't necessarily mean using the same secret right? Or am I misunderstanding? Ah, yeah I keep saying passphrase, but it's just what I've chosen as I'm exploring the tool! |
Hey, I didn't really know where to ask this question.
But in reading the docs, I can't quite understand whether stack reference is available for Open Source edition users.
If
Stack A
tries to refer toStack B
which uses a differentpassphrase
to encrypt its values, or aProject A -> Stack A
tries to refer toProject B -> Stack B
, how would the current stacks context with somePULUMI_CONFIG_PASSPHRASE=passphrase1
env var know how to decrypt some secret or output value from the other stack?The text was updated successfully, but these errors were encountered: