mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 19:56:53 +00:00
kevinveenbirkenbach
cf216014e3
- add cli.meta.applications.resolution.combined to resolve run_after + app-only dependencies - add optional --tree output for combined resolution - add cli.meta.applications.resolution.dependencies (app-only) resolver - move run_after resolver to cli.meta.applications.resolution.run_after - update test deploy dependency resolver to use combined module - add unit tests for combined/dependencies/run_after resolvers - minor cleanup: remove stray header comment, fix newline in vars, tidy YAML formatting https://chatgpt.com/share/696ca531-9644-800f-98c0-bae58c0aff41
Shared Utility Code (module_utils/) for Infinito.Nexus
This directory contains shared Python utility code (also known as "library code") for use by custom Ansible modules, plugins, or roles in the Infinito.Nexus project.
When to Use module_utils
- Shared logic: Use
module_utilsto define functions, classes, or helpers that are shared across multiple custom modules, plugins, or filter/lookups in your project. - Reduce duplication: Centralize code such as API clients, input validation, complex calculations, or protocol helpers.
- Maintainability: If you find yourself repeating code in different custom modules/plugins, refactor it into
module_utils/.
Examples
- Shared HTTP(S) connection handler for multiple modules.
- Common validation or transformation functions for user input.
- Utility functions for interacting with Docker, LDAP, etc.
Usage Example
In a custom Ansible module or plugin:
from ansible.module_utils.infinito_utils import my_shared_function
When not to Use module_utils
- Do not place standalone Ansible modules or plugins here—those go into
library/,filter_plugins/, orlookup_plugins/respectively. - Only use for code that will be imported by other plugins or modules.