I used the serverless-newrelic-lambda-layers plugin to add the new relic lambda layer to my functions.
I had already created the NEW_RELIC_LICENSE_KEY in Secrets Manager but after the deployment, the plugin created an environment variable NEW_RELIC_LICENSE_KEY and displayed the key there.
This leads to the new relic agent startup publishing a warning -
> [NR_EXT] Startup check failed: There is both a AWS Secrets Manager secret and a NEW_RELIC_LICENSE_KEY environment variable set. Recommend removing the NEW_RELIC_LICENSE_KEY environment variable and using the AWS Secrets Manager secret.
How can i disable this? I believe this should never be the case and if setting the environment variable is required, the
disableLicenseKeySecret option needs to be set to true.