So like using the `Pulumi Import Resource Operation` <https Pulumi Community #typescript

So like, using the `Pulumi Import Resource Operati...

mysterious-wolf-74677

11/04/2021, 9:01 PM

So like, using the

Pulumi Import Resource Operation

(found here) do we have to include the

{name: <resource name>}

in the

args

? Doesn't

{import: <resource name>}

take care of that? So you can just do something like

Copy code

const foo = new aws.iam.User('foo', {}, { import: 'foo' })

little-cartoon-10569

11/04/2021, 9:09 PM

The

import

opt is not related to name at all, only to import ID. Import ID is defined by the importing code, and may include related IDs that don't belong to the resource.

little-cartoon-10569

11/04/2021, 9:09 PM

For example, a security group rule has this import ID:

Security Group Rules can be imported using the security_group_id, type, protocol, from_port, to_port, and source(s)/destination(s) (e.g. cidr_block) separated by underscores (_). All parts are required.

little-cartoon-10569

11/04/2021, 9:09 PM

Also, resources don't necessarily have a Name arg. Some do, some don't. And what that name means depends on the resource.

little-cartoon-10569

11/04/2021, 9:11 PM

For many resources, you don't have to provide a name arg if you're not importing, and then Pulumi generates a name from the 1st parameter plus a random bit. This will obviously never match what's in the cloud.

little-cartoon-10569

11/04/2021, 9:11 PM

So to prevent this mismatch, you pretty much always have to provide the Name arg for any resource that support it, when importing.

Open in Slack

Previous Next