Files
computer-playbook/library
kevinveenbirkenbachandClaude Opus 4.7 4d90bcb7f3 fix(database_query): prefer mariadb CLI, fall back to mysql when missing
Modern MariaDB images (>=11) dropped the `mysql` symlink, so the
hardcoded `mysql` binary in the mariadb engine spec started failing
with rc=127 ("executable file not found") — visible e.g. in the
Pixelfed users-table check looping through its `until` retries.
Switch `_ENGINES["mariadb"]` to an ordered `binaries=("mariadb",
"mysql")`, try them in sequence, and only fall back when the OCI
runtime reports the exact binary we tried missing — engine-side
rc=127s (SQL errors etc.) are not masked.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-18 01:09:02 +02:00
..

Custom Modules (library/)

This directory contains project-specific Ansible modules used by Infinito.Nexus.

What Belongs Here

Use library/ for idempotent module logic that represents concrete automation actions.

Typical cases:

  • managing resources that have no suitable built-in/community module,
  • wrapping internal APIs or internal infrastructure semantics,
  • implementing reusable module interfaces for role/playbook consumption.

What Does Not Belong Here

  • Shared helper code used by multiple modules/plugins goes to utils/.
  • Jinja transformations belong to plugins/filter/.
  • Runtime value retrieval belongs to plugins/lookup/.
  • Task execution wrappers belong to plugins/action/.

Usage

Ansible searches library/ for custom modules. In playbooks, call them like built-in modules.

- name: Run a custom Infinito module
  infinito_custom_module:
    option_one: value
    option_two: value

Implementation Notes

  • Keep modules idempotent and predictable.
  • Validate input early and return structured failure messages.
  • Move duplicated helpers into utils/.

Shebang Requirement for Custom Modules

Files in library/ should use:

#!/usr/bin/python

Ansible rewrites this interpreter path to the configured host interpreter for module execution.

References