No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

They won't always been known, since the other stack could be running at the same time. Pulumi has to support this case.

Generally, outputs from StackReferences are used as inputs for other resources, so this problem doesn't occur. Can you split your outputs to be a collection of outputs, instead of an output that is a collection?

That way, each output can be used directly as an input.

My equivalent code exports `privateSubnet1Id`, `isolatedSubnet2Id`, etc.

&gt; They won't always been known, since the other stack could be running at the same time. Pulumi has to support this case
ah ok, that makes sense

&gt; Generally, outputs from StackReferences are used as inputs for other resources
yeah thats typically what happens for me as well but in this case I need to do a foreach over both subnet IDs and route table IDs which i guess isn't possible without an `apply()`

Yes, if you export a complex output then you're likely to have to handle it either in an apply, or in a custom provider.

Either rework your "source" stack to export simple outputs, or add the complex code in your "destination" stack.

no worries, thanks for your help (yet again :D)