Skip to content

fix(logs): fix infinite retention for jsii users #3250

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

Merged
merged 1 commit into from
Jul 12, 2019

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Jul 9, 2019

The retention period was still accepting the value Infinity for
"infinite retention", even though the property has been changed to an
enum instead of number.

Even though this apparently works for TypeScript customers, jsii
customers will not be able to pass in a number where an enum value
is expected, and so won't be able to configure infinite retention.

Add an INFINITE value to the enum.


Please read the contribution guidelines and follow the pull-request checklist.

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

The retention period was still accepting the value `Infinity` for
"infinite retention", even though the property has been changed to an
enum instead of `number`.

Even though this apparently works for TypeScript customers, jsii
customers will not be able to pass in a number where an enum value
is expected, and so won't be able to configure infinite retention.

Add an `INFINITE` value to the enum.
@rix0rrr rix0rrr requested a review from a team as a code owner July 9, 2019 09:01
@rix0rrr rix0rrr merged commit 0b1ea76 into master Jul 12, 2019
@rix0rrr rix0rrr deleted the huijbers/loggroup-infinite-retention branch July 12, 2019 08:48
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 27, 2019
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants