mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
kevinveenbirkenbach
7a3c44b013
- Remove alias-based group name handling from get_deployment_types_from_groups - Make DEFAULT_RULES the single source of truth for server/workstation/universal - Determine "universal" strictly as invokable roles not matched by server/workstation - Update unit tests to reflect invokable-based semantics This aligns Ansible filters and CLI behavior and avoids inventory-specific heuristics. https://chatgpt.com/share/698b8125-d2a0-800f-9fbd-f3f9c8bc5023
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.