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
While this is offered as a feature, it essentially leaks the license key to environment variables when it's not managed by the initial cloudformation deployment.
We have many lambdas and reuse some of the license keys so not every stack can recreate the secret in a cross-account scenario.
You should allow us to be able to disable the templating of the environment variable NEW_RELIC_LICENSE_KEY completely.
I propose that a variable similar to the disableLicenseKeySecret is added to the options or a selfManagedSecret/selfManagedSSM is added in order to allow the license key not be leaked in the environment variables of the lambda function.
i'd be more than happy to propose a PR.
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion. We will take this task in the coming week, due to some other tasks already planned ahead. In the meantime, if you get some time and want to assist with a proposed PR, we would welcome it. Thank you so much!
While this is offered as a feature, it essentially leaks the license key to environment variables when it's not managed by the initial cloudformation deployment.
We have many lambdas and reuse some of the license keys so not every stack can recreate the secret in a cross-account scenario.
You should allow us to be able to disable the templating of the environment variable
NEW_RELIC_LICENSE_KEY
completely.I propose that a variable similar to the
disableLicenseKeySecret
is added to the options or aselfManagedSecret/selfManagedSSM
is added in order to allow the license key not be leaked in the environment variables of the lambda function.i'd be more than happy to propose a PR.
The text was updated successfully, but these errors were encountered: