serverless-plugin-log-retention icon indicating copy to clipboard operation
serverless-plugin-log-retention copied to clipboard

Control the retention of your serverless function's cloudwatch logs.

Results 9 serverless-plugin-log-retention issues
Sort by recently updated
recently updated
newest added

semver module for serverless-plugin-log-retention is old. npm audit report shows that it is high on vulnerability.

The package `semver` version 5.4.1 has a security issue and allows attackers to do a **ReDoS**. Can you please update that package to the latest version ? https://github.com/serverless/serverless-plugin-log-retention/blob/master/package.json#L27

I want to modify the log retention period based on which env my lambda is deployed for. The below is my serverless.yml code. ``` functions: myAPI: name: ${self:service}-${self:custom.stage}-api handler: build/lambda.handler...

If the project contains none aws resources, the log retention is not set, this happens due to a bug in the implementation logic.

When deploy with serverless v2, I got the following warning: ``` Serverless: at 'functions.timeZoneCollector': unrecognized property 'logRetentionInDays' ``` I believe this caused by introduction of schema validation in v2: https://www.serverless.com/framework/docs/providers/aws/guide/plugins/#extending-validation-schema...

When looking for a solution to set log retention for API gateway, I found that the serverless framework provides it's own `logRetentionInDays` parameter: https://www.serverless.com/framework/docs/providers/aws/guide/serverless.yml#general-function-settings That is used for lambda log...

I'm using plugin `serverless-plugin-log-retention` and don't work. Don't have `"RetentionInDays"` code snippet cloudformation ``` "HelloLogGroup": { "Type": "AWS::Logs::LogGroup", "Properties": { "LogGroupName": "/aws/lambda/test-log-retention-plugin-dev-hello" } } ``` serverless.yml ```yaml service: test-log-retention-plugin package:...

After CF stack deletion, the log group may be re-created by CW service, since logs are delivered with some delay, after Lambda invocation. It may cause a problem when you...