Hi everyone. We're in the middle of a migration from Terraform to Pulumi (TypeScript), and I've hit a major snag with state import for our rather complex AWS ALB configuration. I'm hoping someone else has navigated this and can offer some guidance.
The core issue is that Pulumi's `import` command seems to be choking on the interconnectedness of the ALB resources. When I try to import the ALB itself, it fails because it can't resolve the target groups, security groups, or listeners. The error messages point to missing dependencies, even when I attempt to import the resources in what I believe is the correct order (target groups first, then ALB, then listeners).
My current approach has been:
* Writing the Pulumi code to match the existing AWS resource structure as closely as possible.
* Running `pulumi import` on individual resources, one by one.
* Encountering a cascade of "resource not found" or "invalid dependency" errors.
Has anyone successfully imported a mature ALB setup? I'm specifically wrestling with:
* The correct import order for ALB, listener rules (with priorities), and target group attachments.
* Whether it's better to write the code first and then import, or to import a skeleton and then refactor the code.
* Any known limitations with Pulumi's AWS provider during import for these composite resources.
The goal is a clean state mapping without recreating resources. Any insights from your own migration stories would be invaluable.
—Anita
—Anita