FLEX-WP-0037: pin flex-auth-ops-warden to main-9132f9b (agt-custodian registry)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

values/ops-warden.yaml and its generated twin values/access-engine/ops-warden.yaml
move from sha256:138aa347 (main-3de72fe, rollback target) to
sha256:f7c04991a54ebc5fd2a55939e2f68efc7400a51f8773fb6703487833c65b3893.
No Argo application; rollout is an attended helm upgrade (FLEX-WP-0037-T03).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 605711@bnt-lap001
Assistant-Session: 1f5e2256-181f-49ed-b7b1-a1c34bf37a61
This commit is contained in:
tegwick 2026-10-20 23:03:48 +02:00
parent 9132f9b677
commit b429dcba8a
5 changed files with 16 additions and 5 deletions

View file

@ -60,7 +60,7 @@ agt actor in this fixture).
```task
id: FLEX-WP-0037-T02
status: progress
status: done
priority: high
```
@ -73,6 +73,16 @@ current pin `sha256:138aa3471c46bca6e814691fa1e6520aedda3dffd743e6b09141ab433afd
flex-auth has no Argo Application; the pin is applied by an attended Helm
upgrade, so a pushed pin does not deploy by itself.
Result: CI `build-and-push` for `9132f9b` succeeded; `main-9132f9b` =
`sha256:f7c04991a54ebc5fd2a55939e2f68efc7400a51f8773fb6703487833c65b3893`. The
snapshot extracted from the image layer has the same sha256 as the committed
fixture (`5ee90a82…`). `values/ops-warden.yaml` now pins that digest. Note the
previous pin was built from `main-3de72fe` (2026-08), so this roll also carries
every code change since then; the same image line already serves the fetch pin.
The generated runtime twin `values/access-engine/ops-warden.yaml`
(`access-engine-ops-warden`, FLEX-WP-0036) was regenerated with
`tools/gen_runtime_twins.py` to the same digest; `tests/stage1.sh` passes.
## Attended rollout and smoke
```task