fix: Updated Log Group possible retention days #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Some Retention settings were missing and they are now offered by AWS CloudWatch Logs.
Motivation and Context
While working on a HIPAA related project, I tried to setup the retention days to
2192
(6 years), and that’s when I got the validation error:The numbers now match against AWS Console and most importantly also with
aws_cloudwatch_log_group
parameters on AWS Provider.Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectsI tested using the Module with both
0
and2192
values.pre-commit run -a
on my pull request