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]>
30 lines
951 B
YAML
30 lines
951 B
YAML
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: my-plugin-config
|
|
data:
|
|
plugin.yaml: |
|
|
apiVersion: apps.hanzo.ai/v1alpha1
|
|
kind: ConfigManagementPlugin
|
|
metadata:
|
|
name: my-plugin
|
|
spec:
|
|
version: v1.0
|
|
init:
|
|
command: [sh , -c, 'echo "params: $CD_APP_PARAMETERS"']
|
|
generate:
|
|
command: [jq, -n, '{"kind": "ConfigMap", "apiVersion": "v1", "metadata": { "name": env.CD_APP_NAME, "namespace": env.CD_APP_NAMESPACE, "annotations": {"test": "annotation test", "KubeVersion": env.KUBE_VERSION }}, "data": { "params": env.CD_APP_PARAMETERS } }']
|
|
discover:
|
|
fileName: "./subdir/s*.yaml"
|
|
parameters:
|
|
static:
|
|
- name: string-param
|
|
string: default-string-value
|
|
- name: array-param
|
|
array: [default, items]
|
|
collectionType: array
|
|
- name: map-param
|
|
map:
|
|
some: value
|
|
collectionType: map
|