-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(dynamodb): add pointintimerecoveryspecification and deprecate old #32857
Conversation
…intintimerecovery
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #32857 +/- ##
=======================================
Coverage 81.38% 81.38%
=======================================
Files 222 222
Lines 13695 13695
Branches 2412 2412
=======================================
Hits 11145 11145
Misses 2271 2271
Partials 279 279
Flags with carried forward coverage won't be shown. Click here to find out more.
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just some minor changes and I'm happy to approve once fixed.
* | ||
* @default - point in time recovery is not enabled. | ||
*/ | ||
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification | undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification | undefined; | |
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification; |
const pointInTimeRecovery = props.pointInTimeRecovery ?? this.tableOptions.pointInTimeRecovery; | ||
|
||
const pointInTimeRecoverySpecification: PointInTimeRecoverySpecification | undefined = | ||
props.pointInTimeRecoverySpecification ?? | ||
this.tableOptions.pointInTimeRecoverySpecification ?? | ||
(pointInTimeRecovery !== undefined | ||
? { pointInTimeRecoveryEnabled: pointInTimeRecovery } | ||
: undefined); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to check if both properties are used and throw an error instead of silently having one taking precedence over another.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's what I had initially. I'll put it back in. Thanks for taking the time to review.
* | ||
* @default - point in time recovery is not enabled. | ||
*/ | ||
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification | undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification | undefined; | |
readonly pointInTimeRecoverySpecification?: PointInTimeRecoverySpecification; |
@@ -1180,6 +1190,12 @@ export class Table extends TableBase { | |||
|
|||
const { sseSpecification, encryptionKey } = this.parseEncryption(props); | |||
|
|||
const pointInTimeRecoverySpecification: PointInTimeRecoverySpecification | undefined = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above comment.
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
1 similar comment
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
1 similar comment
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
Moved to #33059 |
Comments on closed issues and PRs are hard for our team to see. |
…intintimerecovery
Issue # (if applicable)
Closes #32786
Reason for this change
New feature of DynamoDB
Description of changes
Added pointInTimeRecoverySpecification which takes
pointInTimeRecoveryEnabled
andrecoveryPeriodInDays
.Deprecated
pointInTimeRecovery
as it could not takerecoveryPeriodInDays
Describe any new or updated permissions being added
<!— What new or updated IAM permissions are needed to support the changes being introduced ? -->
Description of how you validated changes
Integ and Unit tests
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license