-
Notifications
You must be signed in to change notification settings - Fork 598
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
newrelic deployments
does not work with newly created API keys
#715
Comments
Hello @Arkham, I tried using the I'm not very familiar with our rest API, so I'll need to reach out to that team and see if they can help me understand what's going on here and why our rake command isn't working properly. Thank you for bringing this to our attention |
I've spoken with the team that handles our API backend and learned some more about what's going on. So basically, the API that the rake task is using is actually going to a different endpoint than the manual API does. There are also a couple types of license keys, and it looks like the API that the rake command communicates with wasn't updated on the backend to accept one of these newer types of license keys, which is why the rake task fails with certain license keys. They weren't aware of the issue either, so thank you very much for reporting this problem, they are looking into the changes needed to solve the issue. In the meantime, if anyone else encounters this issue, the best workaround for now is to use the API manually to record your deployments until the API backend is updated. Please see the API documentation here for more details about how to use this API. (Internal Ticket - link) |
We are keeping this open for now to provide awareness of the issue. This issue will be closed when the internal ticket closes. |
Hi! Is there any progress on this issue? |
Hi @sy-hash. Thanks for following up on this one. Here are some updates:
I will discuss these updates with the rest of the Ruby agent team and if we have anything additional to add we will share it here. Thank you very much for your interest and patience. |
@fallwith |
Maintainers: The Python agent makes use of an I'm thinking we have it work like this:
|
newrelic deployments
only work with the original license key that came with the account.Description
We have recently cycled our NewRelic License Key and updated
config/newrelic.yml
.Running
newrelic deployments -e production -r 1234567890 'Testing new api key'
now yields:After reverting the key inside
config/newrelic.yml
to the previousINGEST - LICENSE
key the command works again.Expected Behavior
Should record the deployment.
Troubleshooting or NR Diag results
Posting to the API manually works with the newly created key:
The text was updated successfully, but these errors were encountered: