Telegram receiver missing bot_token_file config option. #3431
Description
What did you do?
Trying to deploy Telegram receiver securely via GitOps
What did you expect to see?
A bot_token_file parameter.
Slack receiver has a api_url_file param. This allows me to deploy and map a Kubernetes Secret mounted in /etc/alertmanager/secrets.
The Telegram receiver doesn't support that. Now I have to move my entire config to a secret.
EDIT: Should have searched, already implemented in #3226