Files
computer-playbook/filter_plugins
kevinveenbirkenbach c24b1044ae fix(domains): respect AUTO_BUILD_ALIASES when generating redirect mappings
- Do not auto-generate default alias (<entity>.<primary>) when AUTO_BUILD_ALIASES is false
- Only use explicitly defined aliases unless auto-build is enabled
- Treat empty server.domains as opt-out when auto-build is disabled
- Update unit tests to reflect strict alias semantics
- Clarify behavior with inline documentation and comments

https://chatgpt.com/share/697d4994-7690-800f-8987-296ce7215559
2026-01-31 01:15:11 +01:00
..
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
…
2025-12-29 20:37:47 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00
2025-12-17 16:37:21 +01:00

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.

Further Reading