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.8 KiB
Executable File
The notification services represent integration with services such as slack, email or custom webhook. Services are configured in cd-notifications-cm ConfigMap
using service.<type>.(<custom-name>) keys and might reference sensitive data from cd-notifications-secret Secret. Following example demonstrates slack
service configuration:
service.slack: |
token: $slack-token
The slack indicates that service sends slack notification; name is missing and defaults to slack.
Sensitive Data
Sensitive data like authentication tokens should be stored in <secret-name> Secret and can be referenced in
service configuration using $<secret-key> format. For example $slack-token referencing value of key slack-token in
<secret-name> Secret.
Custom Names
Service custom names allow configuring two instances of the same service type.
service.slack.workspace1: |
token: $slack-token-workspace1
service.slack.workspace2: |
token: $slack-token-workspace2
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
annotations:
notifications.apps.hanzo.ai/subscribe.on-sync-succeeded.workspace1: my-channel
notifications.apps.hanzo.ai/subscribe.on-sync-succeeded.workspace2: my-channel
Service Types
- AwsSqs
- GitHub
- Slack
- Mattermost
- Opsgenie
- Grafana
- Webhook
- Telegram
- Teams (Office 365 Connectors) - Legacy service (deprecated, retires March 31, 2026)
- Teams Workflows - Recommended replacement for Office 365 Connectors
- Google Chat
- Rocket.Chat
- Pushover
- Alertmanager