Bot token is printed in logs

[lolgab]

Since Telegram requires the bot token to be in the path, it gets logged in the logs, which can cause token leaks when application logs are stored.
It would be nice if the tokens in the paths were replaced with ******** like:

Request method=POST uri=https://api.telegram.org/bot12341234:************/deleteWebhook headers=Content-Length: 26,Content-Type: application/json,Accept: application/json threw an exception on attempt #1. Giving up.

[johnspade]

Thanks for the report! I'm not sure if it's that easy to fix, since the http4s client creation is not under Telegramium's control. If I understand correctly, in your case the client is using Retry Middleware? You can set the logRetries = false parameter to disable these messages. There is an open issue in the http4s repository regarding this problem: http4s/http4s#6597.