collections

To pin Ansible collection versions, you define the required modules and versions in a requirements.yml file and execute the installation workflow. This guarantees a deterministic state by ensuring the control node only installs the exact collection versions specified before playbook execution.

Managing Ansible collections on a control node is best handled through a script-driven workflow that installs, lists, verifies, and scaffolds external modules. This approach ensures required content is present and prevents state drift in long-running runners and CI pipelines.

Yes, you can verify installed Ansible collections and list the current state on the control node. This verification process prevents drift in long-running runners and CI pipelines by checking that the active environment matches the pinned requirements.

Scaffolding new Ansible collections involves using the provided script workflow to prepare namespaces for distribution. This creates the necessary structural foundation to reuse and share external modules, plugins, and playbooks across multiple projects.

The workflow applies to playbooks and CI environments that rely on external modules and requires a requirements.yml file for deterministic state. It automates the management of Ansible collections on the control node using a script-driven approach.