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

HELP! It seems that changing aws:rds:SubnetGroup *description (!!!)* is causing an aws:rds:ClusterInstace replacement. This is insane!
We tried different pulumi/aws versions: 1.7.0 - 1.14.0 - happens on all of them.

Note that in pulumi/aws 1.8.0 there is a change to subnetgroup description so we are currently stuck on 1.7.0 due to this breaking change.

Hi <@UMCP02GPL> 

Unfortunately, as far as I can tell, changing a description of the subnet group isn’t actually supported by the aws cli or the sdk And this why Pulumi has this limitation 

<https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-subnet-group.html|https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-subnet-group.html>

Can you edit the description in the AWS console? If so then you can use Pulumi refresh to get that change 

Also <@UMCP02GPL> you can pass ignoreChanges to the CustomResourceOptions to say ignore changes to description 

Eg (writing on my phone)

Const myGroup = new aws.rds.SubnetGroup(“my-group”,{},{
  ignoreChanges: [“description”]
})

<@UHTP242EB> Thanks for your quick reply! Indeed the ignoreChanges worked as expected :muscle: Thank you!

I would recommend adding a warning in pulumi-aws CHANGELOG on version 1.8.0 since there is a forced change to the default description which can cause this issue:
<https://github.com/pulumi/pulumi-aws/blob/master/CHANGELOG.md#180-2019-11-07>

I’m glad that worked - I’ll add an entry to the changelog to use ignoreChanges - sorry that caught you :/

Feel free to let me know if there are any other issues

Maybe we should back out the description change there 

<@UB8A66MPS> it was like 5 releases ago - maybe more :(