mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-13 14:16:46 +00:00
kevinveenbirkenbach
c3c54ce043
- Extract shared TLS logic into module_utils/tls_common - Introduce cert_plan lookup for certificate paths and SAN computation - Simplify tls_resolve to strict protocol/port/domain resolution only - Add global self-signed certificate scope covering all domains - Mount self-signed cert base into OpenResty container - Update Nginx templates to use cert_plan for ssl_certificate paths - Add comprehensive unit tests for tls_common, tls_resolve, and cert_plan https://chatgpt.com/share/6972c568-9e8c-800f-b89a-a0061966f9a8
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.