-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Updated to use the new newrelic v2 api #5341
Updated to use the new newrelic v2 api #5341
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
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.
Thanks for your contribution! Please note that there was an earlier PR to fix this (#1501).
Please add a changelog fragment.
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.
@wliao008 thanks for the contribution! I made a couple of comments, most of them are nit-picking.
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
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #5354 🤖 @patchback |
* updated to use the new newrelic v2 api * check that application_id is set * indenting issue * added back app_name * fix import ordering * resolving various spellings & wordings * fixed wordings * validate_certs * fixed unreachable code (cherry picked from commit 7e2a6cf)
SUMMARY
This fixes #4758
ISSUE TYPE
COMPONENT NAME
community.general.newrelic_deployment
ADDITIONAL INFORMATION
The NewRelic v2 API has changed,
app_name
is gone,application_id
is now required. See https://docs.newrelic.com/docs/apm/new-relic-apm/maintenance/record-monitor-deployments/