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

Set up to 10 custom headers on go client #613

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

addshore
Copy link

@addshore addshore commented Aug 19, 2024

Should fix #483

I was not able to test this in a development environemtn myself, however the code change si rather straight forward.
Open to ideas to better read the JSON, but ultimately I believe this should work for 99.9% of folks cases and isn;t too ugly.
We could always up the limit from 10 with little effort.
I'd be happy to have #483 resolved!

@addshore
Copy link
Author

@Slach I see you active, I wonder if you might be able to take a look at this?

@Slach
Copy link
Collaborator

Slach commented Sep 3, 2024

sorry for late response, failures in e2e test is not related to your PR, to ensure could you merge latest comits from master something like git pull upstream master?

@addshore
Copy link
Author

@Slach it looks like CI is all good now!

@Slach
Copy link
Collaborator

Slach commented Sep 18, 2024

yep, but actually it conflicts with #594

and i don't like implementation about 10 headers
we could make better to allow add any custom headers without 10 restriction

@addshore
Copy link
Author

Aaah, is #594 removing this go code entirely? If so, any ETA on when that PR might end up landing? And does it include custom headers within its client?

@Slach
Copy link
Collaborator

Slach commented Sep 19, 2024

sorry we don't provide any ETA
and yes, typescript-backend shall support custom headers, even for alerts

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

Successfully merging this pull request may close these issues.

Configured custom headers not being used in Grafana managed alerts
2 participants