01/31/2023, 1:30 PM
I have a pulumi stack which includes a RDS cluster, which I tried out serverless instanceClass on. but reverted back to t3.medium, and that works fine, the cluster instances are now db.t3.medium. BUT, every time i run
pulumi up --refresh
now it tries to change the following:
serverlessv2ScalingConfiguration: {
        maxCapacity: 16 => 0
        minCapacity: 2 => 0
instanceClass                     : "db.serverless" => "db.t3.medium"
the update succeeds fine, the instancesclass isnt serverless and havent been for a long time, but its annoying that it reports drift every time. How can I fix this?