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 use Pulumi to manage AWS infrastructure and need to upgrade the pulumi/awsx package from 0.x to 1.x to support new features. However after updating the package and getting 'pulumi up' working again without errors (this mainly involved updating some interface usage) pulumi wants to replace the VPC which basically triggers a replacement of most of the infrastructure. Just wondered if others had this issue and any pointers to migration guides?

In your existing code which uses `<http://awsx.ec2.xyz|awsx.ec2.xyz>`, change it to `<http://awsx.classic.ec2.xyz|awsx.classic.ec2.xyz>`. Everything should go back to normal.

You can use the new <http://awsx.xyz|awsx.xyz> namespaces for the new features, and the original resources for the resources you don't want to migrate.