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

Screenshot 2025-09-16 at 5.00.01 PM.png

Screenshot 2025-09-16 at 5.00.47 PM.png

Screenshot 2025-09-16 at 5.00.27 PM.png

`pulumi import` doesn't seem to work: using either the token from pulumi registry or what's seen in the preview doesn't work

Check the example here: <https://www.pulumi.com/registry/packages/aws/api-docs/organizations/organizationalunit/>

The syntax is
```pulumi import aws:organizations/organizationalUnit:OrganizationalUnit example ou-1234567```

second screenshot was following the docs; not working / for some reason pulumi could not find the urn

running pulumi up always tries to create the tools-ou but throws an error of Duplicate OU

Import doesn't use a URN, it creates one.

i see; so `example` should be a completely new name instead of what's defined in my pulumi code?

No, remember that Pulumi adds suffices to names, and names go in URNs

You have 2 choices: import without the code, then add the code (less good, imo), or don't use `pulumi import` and instead add the `import` opt to the existing code.

`pulumi import` is used when you don't have the code already.

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

Note especially the last line of that page:
&gt; Once a resource is successfully imported, remove the import option because Pulumi is now managing the resource.

I shall never buy another t-shirt or hoodie.