Closed michaeldel closed 4 years ago
Telegram is fine by me, it's a sufficiently large platform that justifies having a notifier integrated in Vigil. Thanks for this!
I will build a release today, I have some issues to process in my Vigil backlog first for the next release.
Done, v1.15.0
has been released.
Even though I know you are not fond of adding more notifiers, I added this one for my own needs so why not attempting to merge it here. To me, Telegram is popular enough to justify having an interface to it built-in here.
The WebHook notifier is not well suited for interfacing with more complex APIs such as Telegram's, and I did not want to a bridge service as recommended in README just to support this feature.
Configuration remains minimal (bot token and chat id) and results are aggregated in order to keep messages concise. Here is an example:
No extra dependency required, cf
Cargo.toml