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

interested in what responses this gets...

So to reply to my own question, after some digging around GitHub and blog posts the more complex use cases seem to prefer having a separate class for for config and using the config methods for get/require on the individual properties, similar to the first option I posted. Might be useful to someone if they search back on this.