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

In my mind, that's not really something that happens inside the normal flow of a Pulumi program. That's sufficiently exceptional that a separate flow is justified. I'd consider writing a wrapper script for `pulumi stack init` which also calls `pulumi import` a pile of times (and discards the generated code).

So when you init your new stack, it does its best to populate as many resources as it can.