You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues, it hasn't been reported yet
Issue description
A V.4 feature was added that adds Advanced Logging Controls to AWS Lambda. But it includes a titlecased YAML property that breaks the camelcase rules we have. It's LogGroup when it should be logGroup at both the Provider and Function level. It's in the docs, but if it's in the actual implementation, that needs to be fixed as well.
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
A V.4 feature was added that adds Advanced Logging Controls to AWS Lambda. But it includes a titlecased YAML property that breaks the camelcase rules we have. It's
LogGroup
when it should belogGroup
at both the Provider and Function level. It's in the docs, but if it's in the actual implementation, that needs to be fixed as well.https://github.com/serverless/serverless/blob/v4.0/docs/providers/aws/guide/serverless.yml.md?plain=1#L534
Service configuration (serverless.yml) content
......
Command name and used flags
......
Command output
Environment information
The text was updated successfully, but these errors were encountered: