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

You can use `config.getObject` to parse the string value of the config as JSON. Then you can set config to the valid JSON string input you want. 

Alternatively, I’ve seen many folks just encode lists comma separated and then `val.split(‘,’)` to get the array of values. 

I guess that's clever enough for the time being. Cheers

yaml is an awful text protocol because it’s so easy to screw up. And then you end up with stupid stuff like templated yaml.

Personally, I’d add a custom config of my own and not try to extend Pulumi’s

I like the idea of making config actually a resource, means that the dependencies get to be part of the graph.