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

And a side question:

I am exporting an entire k8s cluster as an output (not sure if it’s the best idea). When referencing this output from another project, the whole output is a secret. Why is this? Is this because the output is a complex object that contains a secret (?) then the wrapping object is now a secret?

&gt; Is there a way to generate Typescript types for stack outputs so when using `new pulumi.StackReference` we enjoy an strict schema?
No but it's a good idea. Something we've thought about adding at some point.

&gt; Why is this? Is this because the output is a complex object that contains a secret (?) then the wrapping object is now a secret?
Yup pretty much. You can use "pulumi.unsecret" on specific parts to unsecret them if you want.

That makes sense! Thank you :pray: congrats on our work, it’s a great product

As an aside, we generally recommend exporting specific properties instead of the entire object (so, specific properties of the Kubernetes cluster instead of the entire cluster object).

Yeah! That’s what I end up doing. Much easier, cleaner and I only import/export what I need. Sleek

I had a colleague here at Pulumi describe stack outputs as “the API of the Pulumi project”: expose only what’s needed, and leave the rest as internal implementation details. That was helpful for me, as before that I tended to export everything (just in case I needed it).

That’s a good way to put it indeed! Makes absolute sense