serverless/lib/plugins/create/templates/aws-kotlin-jvm-gradle/build.gradle , because this file have log4j 2.13 version

Are you certain it’s a bug?

• Yes, it looks like a bug

Is the issue caused by a plugin?

• It is not a plugin issue

Are you using the latest version?

• Yes, I’m using the latest version

Is there an existing issue for this?

• I have searched existing issues, it hasn’t been reported yet

Issue description

Hello, good morning, I want to know if you are going to update the version of log4j on the following plugin :plugins/create/templates/aws-kotlin-jvm-gradle/build.gradle , because this file have log4j 2.13 versions:

rg.apache.logging.log4j:log4j-api:2.13.3’, ‘org.apache.logging.log4j:log4j-core:2.13.3’,

thank you.

Service configuration (serverless.yml) content

N/A

Command name and used flags

N/A

Command output

N/A

Environment information

2.69.1

[varun73]

@pgrzesik No problem, I have reverted the aws library change. There should be no overlap now.

[pgrzesik]

@JuanBermudezN I believe it does not include any breaking changes and we should upgrade it in the templates to 2.16.0 at least - PRs are welcome to address that for all our existing templates. Additionally, as @MarinaMeza pointed out, we should also update aws-lambda-java-log4j2 to 1.4.0 which is now the recommended version by AWS:

Independent of this change, we strongly encourage all customers whose functions include Log4j2 to update to the latest version. Specifically, customers using the aws-lambda-java-log4j2 library in their functions should update to version 1.4.0 and redeploy their functions. This version updates the underlying Log4j2 utility dependencies to version 2.16.0. The updated aws-lambda-java-log4j2 binary is available at the Maven repository and its source code is available in Github.

PRs for that change would also be very welcome 🙇