-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_rds: add support for RotateImmediatelyOnUpdate to secret rotation #25365
Comments
Hi @rittneje , thanks for reaching out. since Cloudformation provides the RotateImmediatelyOnUpdate property, addition of parameter like However you could use Escape hatches for now, to set |
Hi @rittneje addRotationSingleUser() literally instantiate SecretRotation class, in which the secret addRotateSchedule() here. addRotationSchedule() accepts RotationScheduleOptions which is defined here. So I believe we should add RotateImmediatelyOnUpdate into the RotationScheduleOptions. Before that, Escape hatches as mentioned by @khushail is a quick hack but we definitely welcome PR for it. |
…ecret rotation schedule (#25652) When adding a rotation schedule to a secret, you can specify whether or not the secret should be rotated immediately. This is optional, and by default, the secret will be rotated immediately if rotateImmediatelyOnUpdate is undefined. This PR exposes the rotateImmediatelyOnUpdate property enabling the user to configure this as false if they do not want the secret to be rotated immediately. Configuring this property as being explicitly true will result in the secret being rotated immediately, which is the default behavior. Closes #25365 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
@colifran You did not actually implement this feature request. You only added support into aws_secretsmanager.RotationSchedule. But the need is to add support to aws_rds.DatabaseCluster.add_rotation_single_user. |
Describe the feature
In CloudFormation, AWS::SecretsManager::RotationSchedule contains an optional property
RotateImmediatelyOnUpdate
, which controls whether the secret gets rotated as part of the stack update.When creating a rotation schedule via
add_rotation_single_user
in CDK, there is no way to set this property, so CloudFormation ends up defaulting totrue
.Add an optional parameter to
add_rotation_single_user
to control this property. Probably should be added toadd_rotation_multi_user
as well.Use Case
We don't want the secret to rotate immediately.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.60.0
Environment details (OS name and version, etc.)
Alpine
The text was updated successfully, but these errors were encountered: