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

I consider all this to be expected, which is why I don't use `pulumi import` (we also use only non-default providers). I always write the code manually and use the `importId` opt when importing a resource.

IMO, `pulumi import` is a great shortcut but doesn't save that much time for experienced users. It's often just as fast to write the code by hand and import it. And if the resource is nested inside a component resource (which for me, it _always_ is), then it's faster to do it manually, since I don't have to move the resource and alias it after importing.

<@U012UJTT55M> tell me more about `importId` :smile:

It's the original way imports were managed: it allows you to import an existing resource during normal `pulumi up`. It's an opt, whose value documented at the bottom of every resource doc page, and which you add during your import run of `pulumi up`, then remove immediately afterwards (so Pulumi doesn't try to import it again).

<https://www.pulumi.com/docs/intro/concepts/resources/options/import/>

OMG this would have saved me a lot of time. :face_palm: