telegram polling protocol environment #561
Labels
feature request
New feature or request
Comments
joeyorlando
pushed a commit
that referenced
this issue
Aug 24, 2023
# What this PR does Runs Telegram long polling to get updates. It's enabled by setting `FEATURE_TELEGRAM_LONG_POLLING_ENABLED=True`. That will disable webhook and run separate deployment for telegram long polling. Telegram long polling is not very HA mode, but it does not need to expose webhook url to internet and simplifies telegram integration. ## Which issue(s) this PR fixes closes #561 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I noticed before about private server where running Grafana OnCall need use ChatOps/Alert notifications through webhook with self-signed certificate (#530), but what about polling protocol?
I think if we get telegram connections through polling protocol it will be more useful than we trying connect by webhook from private servers. In results there's no need to open external port for receiving messages from telegram bot. :)
The text was updated successfully, but these errors were encountered: