mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Fable 5
1371d01a4f
The sys-service-loader iterates the role-wide static service order, so it asks the service lookup about keys (e.g. the css alias of cdn) that the play-local registry built from applications does not contain. The lookup raised and killed the bootstrap play on every distro. Fall back to the registry read from roles_dir, the same source the loader iterates, so every loader-visible key resolves with its provider role and play-computed flags (false when no consumer is deployed). Canonical aliases aggregate their primary key's consumer flags. A term unknown to both registries still raises. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Custom Lookup Plugins for Infinito.Nexus
This directory contains custom Ansible lookup plugins used within the Infinito.Nexus project.
When to Use a Lookup Plugin
- Load external data: Use lookups to retrieve data from files, APIs, databases, environment variables, or other external sources.
- Context-aware data access: Lookups can access the full Ansible context, including inventory, facts, and runtime variables.
- Generate dynamic lists: Lookups are often used to build inventories, secrets, or host lists dynamically.
Examples
# Load the contents of a file as a variable
my_secret: "{{ lookup('file', '/path/to/secret.txt') }}"
# Retrieve a list of hostnames from an external source
host_list: "{{ lookup('infinito_inventory_hosts', 'group_name') }}"
When not to Use a Lookup Plugin
- If you only need to manipulate or transform data already available in your playbook, prefer a filter plugin instead.