feat: add logRetention option for mergeSchema lambdas with default to… #495
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arnaud-deprez
force-pushed
the
feat/mergeschema-log-retention
branch
2 times, most recently
from
117c8e8 to
1b9e8fc
Compare
arnaud-deprez
force-pushed
the
feat/mergeschema-log-retention
branch
from
1b9e8fc to
8cdbb68
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Currently there is no way to specify the logRetention period for a lambda. As a result, the log stream never expires which can then implies high costs.
About this change
This is a proposal to add this option while leaving the default to 2 years expire.
Additionally, you can configure other properties for the provider like the pollingInterval, etc.