-
Notifications
You must be signed in to change notification settings - Fork 158
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
Fix rds.Instance v5 to v6 migration #4027
Fix rds.Instance v5 to v6 migration #4027
Conversation
Enabling PlanResourceChange=true on v6 of pulumi-aws provider regresses on replacing rds.Instance. It appears that the problem here is that the code has not been completely removing the deprecated "name" property from the old state. This is now fixed and covered by tests.
@@ -3094,6 +3094,7 @@ func ProviderFromMeta(metaInfo *tfbridge.MetadataInfo) *tfbridge.ProviderInfo { | |||
}, | |||
TransformFromState: func(ctx context.Context, state resource.PropertyMap) (resource.PropertyMap, error) { | |||
if _, ok := state["dbName"]; ok { | |||
delete(state, "name") |
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.
It seems that under PlanResourceChange, having "name" hanging around confuses the diff to think it's changing from "something" to "" and that should be a replacement.
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.
looks good
Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
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.
LGTM
Enabling PlanResourceChange=true on v6 of pulumi-aws provider regresses on replacing rds.Instance. It appears that the problem here is that the code has not been completely removing the deprecated "name" property from the old state. This is now fixed and covered by tests.