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

Are there any recommendations for a migration path for VPCs created prior to awsx 1.x? Classic has the method `fromExistingIds` where I could possibly retain the VPC on delete and then look it up by ID but I don't see a way to get an existing `awsx.ec2.Vpc` resource. There also doesn't appear to be a way to import an existing VPC as an `awsx.ec2.Vpc` since it's a `ComponentResource` and there's no import property on `ComponentResourceOptions`.

It'd be great if there was some official documentation that outlined a migration path. Currently the README only suggests that resources may need to be recreated when migrating to 1.x.

FWIW as of awsx@1.0 I ended up dropping awsx for VPC creation entirely, and reproduced the internal structure awsx creates manually (not that hard to do) so that at least the VPC and subnets didn't need to be recreated. It's not that hard to DIY and we also wanted more control for other reasons, so it was OK for us - but we did still schedule downtime to do it