This message was deleted.

sparse-intern-71089

01/27/2020, 11:12 PM

This message was deleted.

handsome-actor-1155

01/27/2020, 11:13 PM

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?

handsome-actor-1155

01/27/2020, 11:15 PM

In case you couldn’t tell, this is for typescript 🙂 My current implementation looks like this: `Pulumi.dev.yaml`:

Copy code

stream-demo-sensor-reading-producer:site:
  - consumerGroupId: consumer-group-0
    endSiteId: 9
  - consumerGroupId: consumer-group-1
    endSiteId: 19

index.ts

Copy code

type Site = {
    consumerGroupId:string
    endSiteId:number
};
const array = config.getObject("site") as Array<Site>;
console.log(array[0].consumerGroupId);

white-balloon-205

01/27/2020, 11:33 PM

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?

handsome-actor-1155

01/27/2020, 11:36 PM

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

handsome-actor-1155

01/27/2020, 11:37 PM

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.

6 Views

Open in Slack

Previous Next

Pulumi Community

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.