limited-art-9054101/24/2024, 7:08 PM
red-match-1511601/24/2024, 7:28 PM
limited-art-9054101/24/2024, 7:47 PM
red-match-1511601/24/2024, 7:53 PM
limited-art-9054101/24/2024, 11:30 PM
red-match-1511601/24/2024, 11:54 PM
limited-art-9054101/25/2024, 12:52 AM
is that reading the stack reference is very long. We actually have very few outputs from the stack that we need and they aren't that sensitive. We want to avoid having one stack pull in another.
We are playing with the idea of creating a
that will manage an environment we create to export certain stack outputs.
We are hoping that loading a small environment will be much quicker than reading a stack.
I saw that there's a pulumi-stacks provider but the documentation didn't seem to indicate that you can only import the outputs you want/need, or if it would be faster than using a StackReference in IaC.
There's little value / difference for us whether a value comes from the config or a stack reference as long as we can decrease the time needed to run
red-match-1511601/25/2024, 3:35 AM
I saw that there's a pulumi-stacks provider but the documentation didn't seem to indicate that you can only import the outputs you want/need, or if it would be faster than using a StackReference in IaC.Oh interesting, yeah the esc provider returns all outputs from a stack. I think an original design did have the ability to only filter certain outputs. As for whether it's faster than using a StackReference in IaC - I'm actually not sure. And I'm surprised to hear accessing stack references is slow - that's probably something we want to look into!