Go to file

Tower Bot e3756ac1d1 tower 0.61.7 — Phase G + delete fall-through to force-delete

Phase G: every Operation now carries (TenantID, ActorUserID, ActorEmail)
stamped at opStore.Create from the request scope. The bell SSE stream
filters per event against the caller's scope before emitting (closes
the cross-tenant leak — non-super-admin users no longer see other
tenants' ops). Get / Cancel / Stream-one return 404 (not 403) when
the caller can't see the op so existence isn't probable across
tenants. List endpoint uses op.TenantID directly (covers in-flight
ops with no Argo App yet); legacy ops with empty tenant fall back
to the Argo lookup so the upgrade is seamless.

Delete leak: cascade-delete failure used to fail the whole flow,
stranding the Gitea overlay repo + DNS A record. Now: cascade
fails → escalate to ForceDeleteApplication (strip finalizers) →
continue to repo + DNS cleanup. Both fail only when ArgoCD itself
is unreachable. Caught when odoo16v2 left tenant-havari/instance-
odoo16v2 orphaned across the smoke test.

Tests + build green.

2026-04-30 12:42:12 +03:00

templates

ingress: route /connect and /teardown to backend (customer-facing token endpoints)

2026-04-29 13:57:51 +03:00

backend-deployment.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail

2026-04-26 20:47:11 +03:00

Chart.yaml

Initial Tower chart

2026-04-26 18:01:44 +03:00

ingressroute.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail