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

Hi, I'm migrating from aws classic v4 to v5 and I'm having trouble with RDS insntace provisioning (<https://www.pulumi.com/registry/packages/aws/api-docs/rds/instance/>). On v5, `name` is deprecated and `db_name` is its replacement. If I just replace `name` with `db_name` while provisioning rds.instance, pulumi thinks I'm changing the value for `db_name` and plan to replace the instance. How can I just adjust the attribute (from name to db_name) without causing a replacement?

Hi there,
Sorry, how does using an alias resolve the issue?

My RDS is a protected resource
If I rename the resource and put the old name in the aliases array then I face the same issue of pulumi wanting to delete my resource

My goal is the same as Diogo’s
I want to just replace `name` with `dbName`
The values will be the same

<@U022ADYFYL8> Did you figure it out? We're running into the same issue where just setting `aliases=[pulumi.Alias(name="old_name")],`  is not enough.