-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration to fixup bridge imports #1103
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets give it a shot.
Happy with this in principle. Have you tested this on a handful of providers locally already? We should probably have a way of tracking a migration roll-out and flagging any issues. |
Tested locally as well as on pulumi/pulumi-gcp#2593 pulumi/pulumi-datadog#683 pulumi/pulumi-cloudflare#955 pulumi/pulumi-random#1345 (I also tried AWS a few times before realizing Anton had already migrated it :)).
@danielrbradley not sure if there's a better way to track, but there are currently 34 uses of the deprecated pf module which we expect to go to zero. I can kick off an "update workflows" actions and then see where things stand after those PRs have had a chance to merge. |
Supersedes pulumi/pulumi-upgrade-provider-action#34.
Adds a migration to update imports to point at new paths introduced by pulumi/pulumi-terraform-bridge#2480 (after that's released).