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

my bad... did not realize some resources go through the standardized kafka APIs whereas others (like users) go through vendor-specific admin APIs

i'll have to swap to using the new support for any terraform provider to use the redpanda one

but my main question is... now that generating pulumi packages from terraform providers is a single command, why are we not seeing more proliferation of `@pulumi/xyz` packages on npm? eg. yesterday i had to generate `@pulumi/b2` and now need to generate `@pulumi/redpanda` - don't get me wrong, I think the new terraform provider support is incredible... just wondering if it might be feasible to simply write a script that iterates over existing terraform providers and auto-published pulumi packages to npm?