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]>
27 lines
879 B
YAML
27 lines
879 B
YAML
apiVersion: v1
|
|
data:
|
|
policy.csv: |
|
|
p, role:user, clusters, get, *, allow
|
|
p, role:user, clusters, get, https://kubernetes*, deny
|
|
p, role:user, projects, get, *, allow
|
|
p, role:user, applications, get, *, allow
|
|
p, role:user, applications, create, */*, allow
|
|
p, role:user, applications, delete, *, allow
|
|
p, role:user, applications, delete, */guestbook, deny
|
|
p, role:user, applicationsets, create, */*, allow
|
|
p, role:user, applicationsets, delete, */*, allow
|
|
p, role:user, logs, get, */*, allow
|
|
g, test, role:user
|
|
policy.overlay.csv: |
|
|
p, role:tester, applications, *, */*, allow
|
|
p, role:tester, projects, *, *, allow
|
|
g, my-org:team-qa, role:tester
|
|
policy.default: role:unknown
|
|
kind: ConfigMap
|
|
metadata:
|
|
labels:
|
|
app.kubernetes.io/name: cd-rbac-cm
|
|
app.kubernetes.io/part-of: cd
|
|
name: cd-rbac-cm
|
|
namespace: cd
|