RDS: "DBCluster not found" if deletionProtection changes

[ctapobep]

Describe the bug

I was getting a very strange error DBCluster not found, even though all the IDs were matching and all. Spent quite a lot of time figuring out that the reason was that deletionProtection changed from false to true. Here's output of cdk diff

Expected Behavior

The DB Cluster is updated to the new deletionProtection. Or at least the error explicitly says that the new settings can't be applied.

Current Behavior

Cryptic "DBCluster not found" error when doing cdk deploy

Reproduction Steps

1. Write a CDK cluster with deletionProtection: true. Example:

        new ServerlessCluster(scope, scope.stackName + "-DB", {
            // DB to connect to when admin user creates the rest of databases. We won't store data in this
            // database though, it's needed only for the initial connection. There could be multiple databases
            // we want to create for different apps & purposes.
            defaultDatabaseName: 'postgres',
            engine: DatabaseClusterEngine.AURORA_POSTGRESQL,
            vpc: networkInfo.vpc,
            vpcSubnets: ...,
            securityGroups: [sg],
            parameterGroup: ParameterGroup.fromParameterGroupName(scope,
                'ParameterGroup',
                'default.aurora-postgresql10'
            ),
            scaling: {
                autoPause: Duration.hours(2), // never pause in PRD, it takes half a min to wake up!
                minCapacity: 2, maxCapacity: 2
            },
            enableDataApi: true, // to be able to run queries from Query Editor in AWS Console
            deletionProtection: true,
            removalPolicy: RemovalPolicy.RETAIN
        });```
2. After it's created, change `deletionProtection` to `false`

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.82.0

### Framework Version

_No response_

### Node.js Version

v18.16.0

### OS

MacOS

### Language

Typescript

### Language Version

_No response_

### Other information

_No response_

[peterwoodworth]

What's your cdk diff output?

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[ctapobep]

I've added cdk diff output to the original post. I can't reproduce the issue outside of that particular stack. What I just noticed is that my DB is called vtlb3-vtlbdbf5332276-4uuqn6ztsud7. I don't know where that 3 came from since the stack name is called VTLB. But my hunch is that this 3 is the culprit. The ID that I give to the cluster in my code is "VTLB-DB". So maybe I just deleted the cluster 🤷

Would be helpful if CloudFormation say which physical ID it was looking for - that would've pointed me in the right direction right away.

[peterwoodworth]

Yeah it's probably not an issue with deletion protection, but some weirdness with names coming from somewhere. If you find a way to reproduce that, let us know. Otherwise, I'm not sure there's much we can help with here.

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.