mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 12:47:04 +00:00
kevinveenbirkenbachandClaude Opus 5.5
7e5da9422c
web-app-matrix (ansible flavor) and web-app-bigbluebutton set compose_mode_force: compose in their role vars, and those vars stay in scope when their front-proxy includes notify the OpenResty handlers. In swarm the handlers' container_address lookup then returned the bare compose name, the validate retried for about 35 s against a container that does not exist and ended ok, and the reload was skipped: 3 of 52 reloads in the WordPress#0 job of fork run 41926377524 (both matrix .onion vhosts), so changed vhosts stayed unserved. The validate, reload and restart handler tasks now clear compose_mode_force at task level (task vars outrank the inherited role vars), as the engine, rdbms and objstore entry points already do, and so do the svc-db-openldap handlers, which the new lint also covers. The proxy_pass lookup applies a caller's override only when the term names the scope's own application_id, because the /logout location rendered inside matrix and BBB vhosts pointed at 127.0.0.1 in swarm. A real ansible-playbook integration test proves both modes and fails without the fix; the new lint keeps every handler lookup of a fixed role clearing the override. 🎯 Fix: 90 % 💥 Break: 4 % 🌱 Efficiency: – ⚡ Speed: – 🛡️ Security: ~100 % 🏆 Score: 86 🚦 Gate: ✅ 90/5, efficiency and speed <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>