mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
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]>
3.0 KiB
Executable File
3.0 KiB
Executable File
NewRelic
Parameters
apiURL- the api server url, e.g. https://api.newrelic.comapiKey- a NewRelic ApiKeymaxIdleConns- optional, maximum number of idle (keep-alive) connections across all hosts.maxIdleConnsPerHost- optional, maximum number of idle (keep-alive) connections per host.maxConnsPerHost- optional, maximum total connections per host.idleConnTimeout- optional, maximum amount of time an idle (keep-alive) connection will remain open before closing, e.g. '90s'.
Configuration
- Create a NewRelic Api Key
- Store apiKey in
cd-notifications-secretSecret and configure NewRelic integration incd-notifications-cmConfigMap
apiVersion: v1
kind: ConfigMap
metadata:
name: cd-notifications-cm
data:
service.newrelic: |
apiURL: <api-url>
apiKey: $newrelic-apiKey
apiVersion: v1
kind: Secret
metadata:
name: <secret-name>
stringData:
newrelic-apiKey: apiKey
- Copy Application ID
- Create subscription for your NewRelic integration
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
annotations:
notifications.apps.hanzo.ai/subscribe.<trigger-name>.newrelic: <app-id>
Templates
revision- optional, The revision being deployed. Can contain a custom template to extract the revision from your specific application status structure.- Defaults to
{{.app.status.operationState.syncResult.revision}}
- Defaults to
description- optional, high-level description of this deployment, visible in the Summary page and on the Deployments page when you select an individual deployment.- Defaults to
message
- Defaults to
changelog- optional, A summary of what changed in this deployment, visible in the Deployments page when you select (selected deployment) > Change log.- Defaults to
{{(call .repo.GetCommitMetadata .app.status.sync.revision).Message}}
- Defaults to
user- optional, A username to associate with the deployment, visible in the Summary and on the Deployments.- Defaults to
{{(call .repo.GetCommitMetadata .app.status.sync.revision).Author}}
- Defaults to
context: |
cdUrl: https://example.com/cd
template.app-deployed: |
message: Application {{.app.metadata.name}} has successfully deployed.
newrelic:
description: Application {{.app.metadata.name}} has successfully deployed