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

This is one of the reasons I recommend TypeScript and interfaces. :disappointed:

Hey <@U02L1LEA5DF> How did you structure your schema.json for this component resource? I’m trying to do something similar and am looking to unwrap the S3 BucketArgs  and use them as inputs to my component resource

I was wondering if you imported these values somehow from the existing pulumi-aws schema.json or if you had to define each input individually?

<@U03JVKL7683> for now, we’re using a mono Git repo that contains both, the reusable components and the calling code. Haven’t yet had to interact with `schema.json`.

But.. please do let me know if you solve it! I don’t know how much longer we’ll be able to get away with the mono repo approach :slightly_smiling_face: