fix: Migrate deprecated logRetention config to logGroup#1666
Open
jeanblanchard wants to merge 1 commit intopepperize:mainfrom
Open
fix: Migrate deprecated logRetention config to logGroup#1666jeanblanchard wants to merge 1 commit intopepperize:mainfrom
jeanblanchard wants to merge 1 commit intopepperize:mainfrom
Conversation
jeanblanchard
force-pushed
the
feat/logretention
branch
from
eb38544 to
ca66b79
Compare
jeanblanchard
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Recent versions of CDK have deprecated the
logRetentionconfiguration inlambda.Function, in favor of an explicitlogGroupconfiguration.The
logRetentionincustom-resources.Provideris not yet deprecated, but is still documented as a 'legacy API', so migrate it too.