feat(rds): scheduling modifications in the next scheduled maintenance window

[Tietew]

Issue # (if applicable)

Closes #33447.

Reason for this change

CloudFormation has added applyImmediately feature to RDS instances.
This allows to schedule modifications in the next scheduled maintenance window.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ModifyInstance.ApplyImmediately.html

Description of changes

Added applyImmediately prop to DatabaseInstanceNewProps and ClusterInstanceOptions.
To schedule modifications, specify applyImmediately: false in instance props.

new rds.DatabaseInstance(this, 'Instance', {
  // ...
  applyImmediately: false,
});

new rds.DatabaseCluster(this, 'Cluster', {
  // ...
  writer: rds.ClusterInstance.serverlessV2('writer', {
    applyImmediately: false,
  }),
});

Note: Currently, applyImmediately is not supported in the cluster configurations.

Describe any new or updated permissions being added

Nothing

Description of how you validated changes

Unit tests and integ tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[Tietew]

Added integration tests verify the applyImmediately property is deployed successfully.
But I'm unsure how to test modifications are actually scheduled.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.17%. Comparing base (f9b28b9) to head (23ebddc).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #33448   +/-   ##
=======================================
  Coverage   82.17%   82.17%           
=======================================
  Files         119      119           
  Lines        6862     6862           
  Branches     1158     1158           
=======================================
  Hits         5639     5639           
  Misses       1120     1120           
  Partials      103      103           

Flag	Coverage Δ
suite.unit	82.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	∅ <ø> (∅)
packages/aws-cdk-lib/core	82.17% <ø> (ø)

[lpizzinidev]

Thanks 👍 Only one minor doc adjustment imo

[GavinZZ]

LGTM, thanks you for the contribution!

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

Pull request has been modified.

[Tietew]

@lpizzinidev Good catch. Fixed.

[Tietew]

Build failed due to #33481

Waiting for @aws-cdk/aws-service-spec v0.1.53 or higher. see #33445 for spec changes.

├[~] service aws-rds
│ └ resources
│    ├[~]  resource AWS::RDS::DBInstance
│    │  └ properties
│    │     └[+] ApplyImmediately: boolean

[GavinZZ]

@Tietew yes, unfortunately we reverted the schema change in the previous release. I'm working on the next release which should include this change.

[Tietew]

@GavinZZ
#33531 is shipped in 2.180.0.
Could you please take a look at this PR again?

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[GavinZZ]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

Pull request has been modified.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 23ebddc
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

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.