Custom Headers in Alerts in golang part

[addshore]

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]

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

[Slach]

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]

@Slach it looks like CI is all good now!

[Slach]

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]

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]

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

[addshore]

I don't know how much overhead releasing a patched version of this go backend would be, but given the go code is going to be entirely replaced in #594 I'd hope we could look past the concerns with this PR

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

I don't disagree it could be better, but you'll throw it away anyway when you come to merge #594, and I assume that PR when it is finished will include a non 10 restricted implementation.

Anyway, looking forward to be able to use this datasource once headers for alerts are supported.