mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
e71e333b12
b64e4a0558gave web-svc-mirror the shared monitoring include so it would appear in the scrape set. That include ends in two locations proxying to the role's own backend, and this role runs no container: it renders a vhost and nothing else. Every deploy that reached its vhost then died in resolve_upstream, twenty-one jobs of one CI run, in both the compose and the swarm phrasing of the same message. What followed was worse than the original gap.514a1fe74bguarded the probe inside healthz.conf.j2, which ninety-six roles render, so a one-role want became a change to shared infrastructure. Three further attempts sharpened that guard, none of them fixed the deploy, and the renders I offered as proof were vacuous: the outer integration guard short-circuited in the context I tested, so the block I was measuring had never rendered. main does not carry the include, cannot reach that code path, and does not fail. The complaint that started this, that mirror carries no app="web-svc-mirror" label, does not appear in the run preceding the include either. It was not a regression and not urgent, and it did not justify touching a template every monitored vhost depends on. So the tree returns to main for both files and the lookup written to support them is deleted. Mirror is unscraped again, which is how it has always been, and now a decision to take deliberately rather than a defect invented from a passing remark in a job log. Measured: both templates are byte-identical to main, nothing references the deleted lookup, and the ansible lint suite passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>