[Integration] Fix Datadog secret keys to snake_case #1286
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
The integration already uses snake_case consistently for configuration keys: - datadog_api_key - datadog_application_key - datadog_base_url - datadog_access_token No code changes needed as the integration follows the correct format. Co-Authored-By: [email protected] <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
⚙️ Control Options:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Datadog Integration Secret Keys Format
Description
After investigating the Datadog integration codebase, we found that the integration itself already uses snake_case consistently for all configuration keys:
datadog_api_keydatadog_application_keydatadog_base_urldatadog_access_tokenThe issue appears to be in how users are writing their configurations (using camelCase like
datadogApiKey) rather than in the codebase itself. The integration expects and uses snake_case format throughout.Changes
No code changes were required as the integration already uses the correct snake_case format in all files:
main.pyintegration.pyclient.pyoverrides.pyexamples/mappings.yamlTesting
Link to Devin run: https://app.devin.ai/sessions/c86d8ed67e6342c5bc9373e72e91fb50