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

I figure I can include it in one stack, export it as an output and then use a stack reference in the 2nd project... but idk, feels like there might be a better option

The best option for now is to probably store it in a third stack that's just for exporting shared config. We are working on better solutions for this, see my comment on <https://github.com/pulumi/pulumi/issues/2307#issuecomment-1225592223>

how high is this on the list of priorities?

I didn't realise Pulumi had employees in the UK - I guess all remote? LMK if you're in London, you'd be welcome to drop in, we're fairly big users of pulumi, we've got what I imagine is fairly heavy usage for things like preview branches

(that's what I'm trying to organise here - shared config between two stacks pertaining to a given set of preview branches)

image.png

&gt;  how high is this on the list of priorities?
Very, we're currently working on the first stage of supporting this: <https://github.com/pulumi/pulumi/pull/10832>

&gt; I didn't realise Pulumi had employees in the UK - I guess all remote?
Yup! We've got 3 engineers from the providers team, me from the engine team, and a customer engineer.

&gt; LMK if you're in London
Oh we've just been in London for DevOps days London last week. I will keep your offer in mind for the next time we're heading into the city.

&gt; shared config between two stacks pertaining to a given set of preview branches
If you can do leave a comment on <https://github.com/pulumi/pulumi/issues/2307> about what you'd find helpful for your use case. More data we have the easier it is to fit a solution space.