Telegram: allow for chat_id to be stored in file same way as bot_token about alertmanager

[a1300]

Hi @freak12techno

I had a similar problem. I solved it by encrypting the chat_id with ansible-vault in the repo. If you choose a strong password it should be no problem to store a secret in the repo.

How encrypted strings with ansible-vault look like in your repo:

telegram_chat_id: !vault |
    $ANSIBLE_VAULT;1.1;AES256
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

To create the ansible-vault string I used:

set +o history

echo -n 'nobody_should_see_this' | ansible-vault encrypt_string
New Vault password: 
Confirm New Vault password: 

set -o history

I encrypted -111111111 with demo password mysecretpassword:

user@machine:~$ echo -n '-111111111' | ansible-vault encrypt_string
New Vault password: 
Confirm New Vault password: 
Reading plaintext input from stdin. (ctrl-d to end input, twice if your content does not already have a newline)

Encryption successful
!vault |
          $ANSIBLE_VAULT;1.1;AES256
          36616365666234623530343532303531383033303563646133373730373862633836376461313531
          6333653435383465303830396238343865336138643031380a393933656234356239376638343138
          30663439393334336264303266383266343963383130303936323561373566623130393730326232
          3435346637303065310a646361363833376461396635666233633066336438646138306465306337
          6564