https://pulumi.com logo
Powered by
#aws
Title
# aws
a

ambitious-father-68746

03/28/2022, 5:44 PM
Hi, I'm trying to switch to v5.1.0 of the Pulumi AWS provider, but I'm hitting a problem with RDS Instaces. The documentation says that 
name
has been deprecated in favor of 
db_name
. Indeed, this shows up when I run Pulumi:
Copy code
├─ aws:rds:Instance         db1              [diff: +name-dbName]; 1 warning
Copy code
warning: name is deprecated: Use db_name instead
But when I actually make the code change to 
db_name
, Pulumi wants to replace all my databases:
Copy code
+-  ├─ aws:rds:Instance           db1                 replace     [diff: +dbName]
I'm not sure how to progress from here, I've checked the state file and it mentions 
dbName
, not 
name
, so I wonder why it complains. Thank you.
b

billowy-army-68599

03/28/2022, 6:04 PM
can you show me the full diff? I think you can work around this with aliases
a

ambitious-father-68746

03/28/2022, 9:19 PM
Copy code
++aws:rds/instance:Instance: (create-replacement)
        [id=database128736]
        [urn=urn:pulumi:precise::lytt::aws:rds/instance:Instance::database]
        [provider=urn:pulumi:precise::lytt::pulumi:providers:aws::provider::634a5466-1c03-4524-a582-fede56d53694]
      + dbName: "database"
    +-aws:rds/instance:Instance: (replace)
        [id=database128736]
        [urn=urn:pulumi:precise::lytt::aws:rds/instance:Instance::database]
        [provider=urn:pulumi:precise::lytt::pulumi:providers:aws::provider::634a5466-1c03-4524-a582-fede56d53694]
    --aws:rds/instance:Instance: (delete-replaced)
        [id=database128736]
        [urn=urn:pulumi:precise::lytt::aws:rds/instance:Instance::database]
        [provider=urn:pulumi:precise::lytt::pulumi:providers:aws::provider::634a5466-1c03-4524-a582-fede56d53694]
I tried setting up some aliases by myself, but it didn't work.
a

acoustic-truck-53557

04/16/2022, 9:32 PM
Hi @ambitious-father-68746, have you managed to solve this?
a

ambitious-father-68746

04/19/2022, 12:10 PM
Yes-ish. I gave it a try again after the latest round of updates and it started working as expected when I switched to 
db_name
. I'm happy.
13 Views
Powered by