This message was deleted.
# general
s
This message was deleted.
b
I think stack references might require that the stacks on both sides have the same passphrase
as long as your IAM user can GetObject in the bucket you should be good on that front I think
c
i'm concerned with a service user having permissions to read the entire state of another stack when all it needs is a couple non-secret outputs from it
b
Unfortunately I don't think you can do partial stack references, but there might be a feature request for it though. Or you could make one
w
correct, this is a limitation... and if you think about it, it makes sense... in order for the stack reference to be able to decode the secrets from the other stack, it will need to know the passphrase of the source stack, as well as it's own. so, in essence, there would need to be a way to pass the source stack's passphrase to the StackReference
b
could be an input on the stack reference "resource" that way you could pass it in and they could be different. And a
PublicStackReference
or something that contains only the outputs and not the secrets isn't a bad idea
1
w
sure, but right now, as you can't, that's the reason it won't be able to do it.
b
yes, we're aware. I was talking about a feature request.
☝️ 2