-
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
chore(dynamodb): explicitly render false
pointInTimeRecovery
#19757
Conversation
Today, if the property `pointInTimeRecoveryEnabled` is either `undefined`, or `false`, we don't render the `pointInTimeRecoverySpecification` property in the Table L1. A customer wants to write an Aspect that checks whether this property has been set, and they cannot differentiate between the "not provided" and "set to `false`" cases. Change the logic to render `pointInTimeRecoverySpecification` even for `false` pointInTimeRecoveryEnabled values. Fixes aws#19748
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…9757) Today, if the property `pointInTimeRecoveryEnabled` is either `undefined`, or `false`, we don't render the `pointInTimeRecoverySpecification` property in the Table L1. A customer wants to write an Aspect that checks whether this property has been set, and they cannot differentiate between the "not provided" and "set to `false`" cases. Change the logic to render `pointInTimeRecoverySpecification` even for `false` pointInTimeRecoveryEnabled values. Fixes aws#19748 ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Today, if the property
pointInTimeRecoveryEnabled
is eitherundefined
, orfalse
,we don't render the
pointInTimeRecoverySpecification
property in the Table L1.A customer wants to write an Aspect that checks whether this property has been set,
and they cannot differentiate between the "not provided" and "set to
false
" cases.Change the logic to render
pointInTimeRecoverySpecification
even forfalse
pointInTimeRecoveryEnabled values.
Fixes #19748
All Submissions:
Adding new Unconventional Dependencies:
New Features
cdk-integ
to deploy the infrastructure and generate the snapshot (i.e.cdk-integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license