This message was deleted.

sparse-intern-71089

02/09/2022, 5:41 PM

This message was deleted.

little-cartoon-10569

02/09/2022, 8:06 PM

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.

little-cartoon-10569

02/09/2022, 8:08 PM

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.

bored-table-20691

02/09/2022, 8:54 PM

@little-cartoon-10569 tell me more about

importId

😄

little-cartoon-10569

02/09/2022, 8:58 PM

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).

little-cartoon-10569

02/09/2022, 8:59 PM

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

bored-table-20691

02/09/2022, 9:01 PM

OMG this would have saved me a lot of time. 🤦

careful-oil-55681

05/06/2022, 10:09 PM

@fresh-librarian-41835 @freezing-flag-53289 ^^

5 Views

Open in Slack

Previous Next

Pulumi Community

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.