mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
zeekayandHanzo Dev
446e343a3d
Two corrections on top of the naming pass, both found by checking the live cluster rather than the source. The rename had silently changed the user-facing annotation key from argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live Applications carry the old key, so deploying that would have ignored every sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*, and universe 575650286 moves the ApplicationSet template that stamps it, so the controller regenerates all 63 consistently. The API group in code said argoproj.io/v1alpha1 in 157 places while the cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are applications.apps.hanzo.ai). Code now matches what is actually served. The legacy applications.argoproj.io/app-name label had ZERO live users, so it went with the rest. foo.argoproj.io test fixtures became foo.example.com — arbitrary test domains should not carry a vendor name. go build ./... exit 0. Co-authored-by: Hanzo Dev <[email protected]>
1.2 KiB
Executable File
1.2 KiB
Executable File
Telegram
- Get an API token using @Botfather.
- Store token in
<secret-name>Secret and configure telegram integration incd-notifications-cmConfigMap:
apiVersion: v1
kind: ConfigMap
metadata:
name: cd-notifications-cm
data:
service.telegram: |
token: $telegram-token
- Create new Telegram channel.
- Add your bot as an administrator.
- Use this channel
username(public channel) orchatID(private channel) in the subscription for your Telegram integration:
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
annotations:
notifications.apps.hanzo.ai/subscribe.on-sync-succeeded.telegram: username
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
annotations:
notifications.apps.hanzo.ai/subscribe.on-sync-succeeded.telegram: -1000000000000
If your private chat contains threads, you can optionally specify a thread id by separating it with a |:
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
annotations:
notifications.apps.hanzo.ai/subscribe.on-sync-succeeded.telegram: -1000000000000|2