Files
f2603ef461 chore: update notifications-engine to f4856710 (#17971)
* update notifications-engine

Signed-off-by: Lukas Peter Aldershaab <[email protected]>

* Fix build of conflicting git-urls libraries

Signed-off-by: Lukas Peter Aldershaab <[email protected]>

* align telegrom dependency with notifications-engine

Signed-off-by: Lukas Peter Aldershaab <[email protected]>

* fix: codegen

Signed-off-by: pashakostohrys <[email protected]>

---------

Signed-off-by: Lukas Peter Aldershaab <[email protected]>
Signed-off-by: pashakostohrys <[email protected]>
Co-authored-by: pashakostohrys <[email protected]>
2024-04-28 09:20:16 +00:00

1.2 KiB
Executable File

Telegram

  1. Get an API token using @Botfather.
  2. Store token in <secret-name> Secret and configure telegram integration in argocd-notifications-cm ConfigMap:
apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-notifications-cm
data:
  service.telegram: |
    token: $telegram-token
  1. Create new Telegram channel.
  2. Add your bot as an administrator.
  3. Use this channel username (public channel) or chatID (private channel) in the subscription for your Telegram integration:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.argoproj.io/subscribe.on-sync-succeeded.telegram: username
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.argoproj.io/subscribe.on-sync-succeeded.telegram: -1000000000000

If your private chat contains threads, you can optionally specify a thread id by seperating it with a |:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.argoproj.io/subscribe.on-sync-succeeded.telegram: -1000000000000|2