-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support nested DD_API_KEY secret in lambda forwarder #851
Conversation
please run |
aws/logs_monitoring/settings.py
Outdated
"Successfully retrieved the Datadog API key from 'DD_API_KEY'." | ||
) | ||
else: | ||
raise ValueError("The secret does not contain the 'DD_API_KEY' field.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed raising a ValueError
here is not properly handled down stream and will lead to an uncaught exception.
I suggest to handle it or simply log an error as we'd still have the DD_API_KEY
set to the default value <YOUR_DATADOG_API_KEY>
which won't work anw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, sorry for the delay. Sounds good, updating.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated, lmk if that looks good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
What does this PR do?
Adds support for nested
DD_API_KEY
in AWS SecretsManager.Motivation
It is common for organizations and individuals to store this in a shared dictionary with other secrets in AWS, which is not currently supported.
Testing Guidelines
Additional Notes
Types of changes
Check all that apply