HTTP notifier headers about helm-charts

[Lowess]

Hi @invernizzie , Thanks for your interest for this repository.

Can you please provide an example of Burrow configuration with the Opsgenie integration (blank out your api key) so that I have an idea of the content of the notifier.<my-notifier>.headers section ?

It looks like Burrow handles well configuration overrides using environment variables as per linkedin/Burrow#486.

To implement the change I would recommend adding the headers section bellow https://github.com/Lowess/helm-charts/blob/master/charts/burrow/templates/burrow-configmap.yaml#L56 to handle non-sensitive headers.

For sensitive data leverage environment variables and Viper.

Regarding the LICENSE. All charts from this repo are under Apache2 license

Feel free to submit a PR I will be happy to help you review it and get it released.

[invernizzie]

Thanks @Lowess, I will definitely add the headers field to the notifier section of the configmap.

The headers for Opsgenie would look like this:

[notifier.opsgenie]
  [notifier.opsgenie.headers]
  Authorization="GenieKey #redacted#"
  Accept="application/json"

I'm not sure if I'd be able to override a single header with and env var given that burrow loads the headers section as a map, but I'll try it out. Otherwise I'll use an env var for the whole section.

[Lowess]

You're right there is a good chance that you need to pass down all the headers as env var except if Viper does some merging logic when the two same keys are defined.