mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
# Conflicts: # docs/contributing/design/services.md # plugins/lookup/applications_current_play.py # plugins/lookup/service.py # roles/sys-stk-backend/lookup_plugins/service_should_load.py # roles/sys-stk-backend/tasks/_load_service.yml # roles/sys-stk-backend/vars/main.yml # roles/sys-svc-compose/templates/base.yml.j2 # roles/sys-svc-mail/tasks/01_core.yml # roles/sys-utils-service-loader/tasks/load_frontend_service.yml # tests/unit/plugins/lookup/test_applications_current_play.py # tests/unit/plugins/lookup/test_service.py # tests/unit/roles/sys-stk-backend/lookup_plugins/test_service_should_load.py
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.