Support global Telegram bot token #4823
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guoard
force-pushed
the
global_telegram_bot_token
branch
from
4b70b50 to
23c962d
Compare
Signed-off-by: Ali Afsharzadeh <[email protected]>
guoard
force-pushed
the
global_telegram_bot_token
branch
from
23c962d to
2028abb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds global configuration support for Telegram bot tokens in Alertmanager. Until now,
telegram_bot_tokenandtelegram_bot_token_filecould only be set per receiver, which could lead to redundant configuration when multiple receivers used the same bot.