Enforce release availability in trusted deployers #135
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/deployer-availability-gate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bake the released availability-probe v4 identity into both trusted deployers. Accept an optional strict JSON policy, run it only after GitOps convergence, preserve its summary in deployment evidence, and make Flux availability failures use the existing automatic rollback path. Argo CD fails closed without mutating Git. Both images advance to v2. All builder checks pass.