Hey everyone 👋 I’m on community rotation this week. • What have people been building with Pulumi lately?

refactoring our hcloud/k3s cluster setup. I was able to separate the cluster to a new stack with kubeConfig as its output, for other stacks to consume. Now working on outputting ssh_config for debugging/emergency access

I was able to separate the cluster to a new stack with kubeConfig as its output, for other stacks to consume.

This is the way!

pulumi.StackReference makes all the difference!

Great work @high-grass-3103! If you're using Pulumi Cloud, I would also suggest taking a look at ESC as an option to meet your needs here. Stack Reference are great but if multiple stacks need that output, you often find yourself having multiple stack references code. With ESC, you could create an environment definition that contains the kubeconfig as a value or a secret and import that definition across any number of stacks. Both are very valid, but just wanted to share some other ways as options should you like one way more than the other

Cool, but I already have a complex object outputted from one project and imported in another 🙂