mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 04:36:40 +00:00
kevinveenbirkenbachandClaude Opus 4.8
2b027bb64a
A bridged addon's <ID>_ADDON_ENABLED flag is now true only when one of its declared bridge partners is in the deployed playwright role set (TEST_E2E_PLAYWRIGHT_APPS): integration specs skip cleanly when the partner is not deployed and assert the real coupling when it is. App-addons without bridges are unaffected; an unresolvable set falls back to the prior enabled-AND-required behaviour (no regression). Adds TestBridgeDeploymentGating (7 cases): partner-deployed, not-deployed, multi-bridge any-match, no-bridge passthrough, disabled stays false, fallback without the set, and string-set splitting. Co-Authored-By: Claude Opus 4.8 <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.