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 as a follow up to this, when accessing such complex config objects in code, do you tend to cast to a defined type? Or parse upon read?

In case you couldn’t tell, this is for typescript :slightly_smiling_face:
My current implementation looks like this:
`Pulumi.dev.yaml`:
```  stream-demo-sensor-reading-producer:site:
  - consumerGroupId: consumer-group-0
    endSiteId: 9
  - consumerGroupId: consumer-group-1
    endSiteId: 19```
`index.ts`
```type Site = {
    consumerGroupId:string
    endSiteId:number
};
const array = config.getObject("site") as Array&lt;Site&gt;;
console.log(array[0].consumerGroupId);```

Yep - something like the above looks like exactly what I would suggest doing given the current support for rich configuration.

Was there anything about this you didn't like, or would have prefered to be different?

I like the approach I have, I guess my main question is do you have any examples on how to make complex config objects defaults during a pulumi new from a template

And was also just trying to see if someone had come up with a different approach other than what I have for managing complex configs.