Skip to content
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

Merged
merged 2 commits into from
Apr 5, 2022

Conversation

skinny85
Copy link
Contributor

@skinny85 skinny85 commented Apr 4, 2022

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 #19748


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • 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 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
@skinny85 skinny85 requested a review from comcalvi April 4, 2022 23:05
@gitpod-io
Copy link

gitpod-io bot commented Apr 4, 2022

@github-actions github-actions bot added feature-request A feature should be added or improved. p2 labels Apr 4, 2022
@aws-cdk-automation aws-cdk-automation requested a review from a team April 4, 2022 23:05
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Apr 4, 2022
@mergify
Copy link
Contributor

mergify bot commented Apr 5, 2022

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-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: a4db41b
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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

@mergify mergify bot merged commit 19664ae into aws:master Apr 5, 2022
@mergify
Copy link
Contributor

mergify bot commented Apr 5, 2022

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).

@rix0rrr rix0rrr deleted the chore/ddb-point-in-time-recovery branch April 6, 2022 08:22
StevePotter pushed a commit to StevePotter/aws-cdk that referenced this pull request Apr 27, 2022
…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*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS. feature-request A feature should be added or improved. p2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws_dynamodb: allow point_in_time_recovery to be IResolvable
3 participants