Telegram push target support

[fjogeleit]

@EsDmitrii first draft of the Telegram Push Target support

• Requires Bot Token and ChatID
• Token can be provided as Secret or MountVolume
• Routing (Channel) support and TLS configuration

telegram:
  chatID: "5235626040"
  token: "XXXXXXX:AAHmp3nGzcXIg-GALcxXFUv3IS5j2clwqiQ"
  minimumPriority: "warning"
  skipExistingOnStartup: true
  customFields:
    cluster: Minikube

[EsDmitrii]

hooray!
awesome!

[EsDmitrii]

can you additionally specify variable for proxy url?
maybe someone will use it in closed systems via proxy ( me :) )

[fjogeleit]

Sure, how will this look like? Currently the API is configured with: https://api.telegram.org/bot%token%/sendMessage. Do you need also some kind of token placeholder, or would the token send as header?

Or should I provide an optional Host instead of token, where your token is included?

[EsDmitrii]

I don't know how to make it in Go, but for python it's looks like this https://github.com/eternnoir/pyTelegramBotAPI#proxy
via apihelper.proxy

[EsDmitrii]

found something for Go https://gist.github.com/tdakkota/2441f2cdd0a96c6ae1f23b70e4e8451d

[fjogeleit]

Ok, I think I understood. So I added a optional Host property, which can be overwritten with a proxy and defaults to the telegram API. This should provide the functionality you need.

The Host can be set over a secret/mountVolume like the token or directly in the config.

telegram:
  host: https://localhost:9090
  chatID: "5235626040"
  token: "XXXXXXX:AAHmp3nGzcXIg-GALcxXFUv3IS5j2clwqiQ"
  minimumPriority: "warning"
  skipExistingOnStartup: true
  customFields:
    cluster: Minikube

[EsDmitrii]

awesome, thank you!

[fjogeleit]

I plan to release it end of the week