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

We're *actively* working on this!
<https://github.com/pulumi/pulumi/issues/7160>

For now the only workaround is to write the resource in your program yourself and use `ResourceOptions.ImportID` to import it in. We're looking at multiple things to improve this.

i'm not familiar with `ResourceOptions.ImportID`, is there a blog post or resource online that details this workaround?

might be helpful to understand how you inform/connect pulumi to existing resources in the interim while these issues are worked out; i tried importing a few other resources and I wasn't able to import anything (as they all had derived/generated fields)

<https://www.pulumi.com/docs/guides/adopting/import/>

Specifically on that page the part about the <https://www.pulumi.com/docs/guides/adopting/import/#pulumi-import-resource-operation|import resource option>.

ok; I think I understand, basically I have to manually define it and link the resource with the ID in AWS via `import` at which point Pulumi will connect the two

any idea on when the CLI import functionality will be fixed?

We hope to ship improvements in the next few releases.

So possibly next Wednesday, but if not I'd really hope we can make the two weeks after that (23rd Feb)

ok, thank you for the update, trying to decide if we are going to use Pulumi for IoC and the import feature was really attractive.