mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Sonnet 4.6
1bcb7cfbb0
Resolve conflicts: - docs/agents/action/iteration.md: keep both new bullets (SERVICES_DISABLED proposal + make test requirement) - docs/contributing/design/services.md: deleted (renamed to docs/contributing/code/services.md in this branch) - group_vars/all/20_services.yml: keep deletion from this branch (req-001) - tests/lint/ansible/roles/test_service_core_first_task_run_once.py: use build_service_registry_from_roles_dir (req-001) with repo_root() from main for robust path resolution Fix broken relative links caused by rename and deletion of files: - docs/contributing/design/architecture.md: services.md → ../code/services.md - docs/contributing/design/exceptions.md: load_frontend_service.yml → load_service.yml - docs/requirements/001-service-registry-refactoring.md: fix paths for unit.md, integration.md, principles.md, documentation.md, AGENTS.md Co-Authored-By: Claude Sonnet 4.6 <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.