mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai

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]>

2026-07-28 16:32:14 -07:00

1.9 KiB

Executable File

Raw Permalink Blame History

Email

Parameters

The Email notification service sends email notifications using SMTP protocol and requires specifying the following settings:

host - the SMTP server host name
port - the SMTP server port
username - username
password - password
from - from email address
html - optional bool, true or false
insecure_skip_verify - optional bool, true or false

Using Gmail

When configuring Gmail as the SMTP service:

username - Must be your Gmail address.
password - Use an App Password, not your regular Gmail password.

To Generate an app password, follow this link https://myaccount.google.com/apppasswords

!!! note This applies to personal Gmail accounts (non-Google Workspace). For Google Workspace users, SMTP settings and authentication methods may differ.

Example

The following snippet contains sample Gmail service configuration:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.email.gmail: |
    username: $username
    password: $password
    host: smtp.gmail.com
    port: 465
    from: $email-address

Without authentication:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.email.example: |
    host: smtp.example.com
    port: 587
    from: $email-address

Template

Notification templates support specifying subject for email notifications:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  template.app-sync-succeeded: |
    email:
      subject: Application {{.app.metadata.name}} has been successfully synced.
    message: |
      {{if eq .serviceType "slack"}}:white_check_mark:{{end}} Application {{.app.metadata.name}} has been successfully synced at {{.app.status.operationState.finishedAt}}.
      Sync operation details are available at: {{.context.cdUrl}}/applications/{{.app.metadata.name}}?operation=true .

1.9 KiB Executable File Raw Permalink Blame History