mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5.5
474849a39c
Two bots bumped the one baudolo version independently. The pip pin updater rewrites the literal package_name pin in roles/svc-bkp-volume-2-local/tasks/01_install.yml and opens a PR scoped to roles/<entry>/, and dependabot bumps the same package in pyproject.toml. Each PR alone splits the pins that tests/lint/repository/dependencies/test_baudolo_pin.py holds equal; #995 merged such a split and turned main's test-lint red until #996, and the next upstream release (7.1.2 is tagged) would repeat it. The version lookup now takes an optional distribution name and returns its exact == pin from [project.dependencies]. The install task asks it for backup-docker-to-local, so pyproject.toml is the only place the version lives, dependabot is the only bot that moves it, and the pip updater no longer finds a literal to bump. The lint now forbids a literal pin in the task and requires the lookup. Co-Authored-By: Claude Opus 5.5 (1M context) <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.