mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
kevinveenbirkenbachandClaude Opus 5
549d272884
Seven lookups read application_id out of the play's variables and every one of them has to template it, because sys-stk-full defines application_id from sys_stk_full_application_id and a dict read returns that unrendered. They did it in five spellings: a public resolve_var, two byte-identical private copies, and inline variants. Nothing named the rule, so it survived as folklore, and a lookup written without knowing it took down three jobs of one run. resolve_var now lives in utils/templating, which is where the six lookups that import it can reach it without pulling in a networking module for a concern that is not networking. utils/networks/lookup_context re-exports it under the alias form, so its own importers are untouched and autodoc still resolves one target. The two private copies go, and so does the fourth copy this branch added to webserver_resource a few commits ago. The private copies guarded value is not None and the public one did not. The canonical keeps the guard: it is narrower than every live caller, each of which passes a defaulted value, so no existing call can reach the branch. The helper had no test at all. Its six behaviours are characterised first, including that a templar raising on an undefined variable leaves the value alone rather than failing the play, which is what the suppression is for. Four inline copies stay. compose_volumes lets a template error propagate where this suppresses it, and mcp_servers only templates a str containing a template marker. Folding those in would change behaviour, which is not a refactor. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
28 lines
894 B
Python
28 lines
894 B
Python
"""Resolve a play variable that may still be a template.
|
|
|
|
A value taken out of the play's variables is raw. A role whose
|
|
``application_id`` is itself a template, as ``sys-stk-full`` sets it from
|
|
``sys_stk_full_application_id``, therefore hands back the unrendered string,
|
|
while the same variable named inside an expression arrives resolved. Every
|
|
lookup that reads such a variable resolves it through here.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import contextlib
|
|
from typing import Any
|
|
|
|
|
|
def resolve_var(templar: Any, value: Any) -> Any:
|
|
"""Template ``value`` when a templar is available, else pass it through.
|
|
|
|
Args:
|
|
templar: the plugin's templar, or None.
|
|
value: the variable as the play holds it.
|
|
"""
|
|
if templar is None or value is None:
|
|
return value
|
|
with contextlib.suppress(Exception):
|
|
return templar.template(value)
|
|
return value
|