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

That is essentially correct. It's currently up to the language to interpret the config values.

I think we have an issue somewhere tracking improving this. Looking...

(current context: "I have a list of CIDR blocks I need passed to a security group")

<https://github.com/pulumi/pulumi/issues/1052> is the issue, though it sort of only hints at the problem.

Yeah, TBH this is the first part of Pulumi that I think I have to completely go around

The current approach is to represent richer values as JSON and use `config.requireObject&lt;&gt;`

Yeah, the config system as it stands could use some work :slightly_smiling_face:

If you have ideas here we'd love to hear them.

I have ideas, but they fundamentally disrespect the multi-platform thing you're going for.

I'm probably just going to do the same thing I do for every other JS app: `require()` a file and throw if its export is not of type `MyStackConfig`.

(When I say "JS" I really mean "TypeScript", and then I already have a self-describing config without having to have one reinvented)

Though, tangentially, the multi-language thing is the thing about Pulumi that worries me the most. Lowest common denominators and all

but... that was so easy to go around... that i'd call that a feature

I think I’d agree with <@UC9MTPN8K> there.

I wouldn't, because now I'm not doing something standard.

Which means I have to document it and have to maintain it.

Users will read Pulumi's docs and have to remember (incurring additional cognitive load) that "we do something different here"

Library vs Framework :slightly_smiling_face: