Skip to content
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

bug: old api-key version for New-Relic service #180

Open
rozdestvenskiy opened this issue May 16, 2023 · 3 comments
Open

bug: old api-key version for New-Relic service #180

rozdestvenskiy opened this issue May 16, 2023 · 3 comments

Comments

@rozdestvenskiy
Copy link
Contributor

rozdestvenskiy commented May 16, 2023

Now new-relic service uses old api key: https://github.com/argoproj/notifications-engine/blob/master/pkg/services/newrelic.go (line 153) req.Header.Set("Api-Key", s.opts.ApiKey)

According to documentation it should be req.Header.Set("X-Api-Key", s.opts.ApiKey) (https://docs.newrelic.com/docs/apis/rest-api-v2/get-started/introduction-new-relic-rest-api-v2/)

Now newrelic module doesn't create deployment markers. Same request with curl works (because of type of header).

@rozdestvenskiy rozdestvenskiy changed the title Fix api-key version for New-Relic service bug: old api-key version for New-Relic service May 16, 2023
@rozdestvenskiy
Copy link
Contributor Author

rozdestvenskiy commented May 16, 2023

Created PR
#181

@lancehudson
Copy link

Do we know if this has been included in a recent ArgoCD release?

@rozdestvenskiy
Copy link
Contributor Author

@lancehudson looks like not. I'm still getting the same error:
time="2023-08-17T08:55:08Z" level=error msg="Failed to notify recipient {newrelic APP_ID} defined in resource argocd/my-app: Post \"api.newrelic.com/v2/applications/APP_ID/deployments.json\": unsupported protocol scheme \"\"" resource=argocd/my-app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants