rds: integ tests fail to deploy due to using deprecated postgres version

[paulhcsun]

Describe the bug

Some existing integ tests within the aws-rds module fail to deploy because they were created with a postgres version that is now deprecated (version <=15.x) and fails with the following error

"Cannot find version 15.2 for postgres (Service: Rds, Status Code: 400, Request ID: 3aaada49-96f7-42bc-ae49-3674c11f56df)"

This is due to the existing snapshots already using the deprecated versions.

Expected Behavior

Should be able to deploy the integ test successfully.

Current Behavior

Fails with the following error

"Cannot find version 15.2 for postgres (Service: Rds, Status Code: 400, Request ID: 3aaada49-96f7-42bc-ae49-3674c11f56df)"

Reproduction Steps

Deploy one of the aws-rds integ tests that still uses a deprecated version of postgres (<=15.x).
i.e.

const parameterGroup = new rds.ParameterGroup(stack, 'ParameterGroup', {
  engine: rds.DatabaseInstanceEngine.postgres({ version: rds.PostgresEngineVersion.VER_15_2 }),
  ...
});

Possible Solution

The solution is to manually delete the corresponding snapshot folder for these tests and update the postgres version to a supported version (currently >=16.x) and rerun the integ test to generate the new snapshots.

Additional Information/Context

No response

CDK CLI Version

2.141.0

Framework Version

No response

Node.js Version

v21.7.1

OS

14.4.1

Language

TypeScript

Language Version

No response

Other information

No response

[daschaa]

I would like to take this issue :)

[Leo10Gama]

@daschaa Thanks for your interest! However, we have someone actively working on this already.

[daschaa]

@Leo10Gama Oh that's unfortunate. Thanks for letting me know.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.