mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
kevinveenbirkenbachandClaude Fable 5
97b1ffddb4
The swarm branch passed values through raw, so a value with interior whitespace (MAIL_FROM_NAME='Infinito.Nexus by ...') landed unquoted in the rendered .env and broke the env parser: the snipe-it service crashlooped at 0/3 until the converge wait failed in every variant. Quote (and escape backslash/double-quote) only when the value contains space/tab/newline; everything else stays raw, so the swarm invariants hold: no compose $$-doubling, raw $ and double quotes preserved, and the playwright --env-file path (docker CLI keeps quotes literal) is unaffected because no playwright env value can contain whitespace. Compose quoting is untouched. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Custom Filter Plugins for Infinito.Nexus
This directory contains custom Ansible filter plugins used within the Infinito.Nexus project.
When to Use a Filter Plugin
- Transform values: Use filters to transform, extract, reformat, or compute values from existing variables or facts.
- Inline data manipulation: Filters are designed for inline use in Jinja2 expressions (in templates, tasks, vars, etc.).
- No external lookups: Filters only operate on data you explicitly pass to them and cannot access external files, the Ansible inventory, or runtime context.
Examples
{{ role_name | get_entity_name }}
{{ my_list | unique }}
{{ user_email | regex_replace('^(.+)@.*$', '\\1') }}
When not to Use a Filter Plugin
- If you need to load data from an external source (e.g., file, environment, API), use a lookup plugin instead.
- If your logic requires access to inventory, facts, or host-level information that is not passed as a parameter.