Files
ansible-role-certificate-au…/requirements.yaml
T
volker.raschekandCopilot 6d465e5dad
Lint Markdown files / markdown-lint (push) Successful in 12s
Ansible Linter / ansible-lint (push) Failing after 55s
Molecule / Molecule (push) Failing after 1m41s
docs: declare the dependency on the collection community.crypto
The role uses openssl_privatekey, openssl_csr, x509_certificate and x509_certificate_info, but neither declared
that collection anywhere nor mentioned it in the readme. A standalone role cannot express collection dependencies in
its metadata, so a requirements file next to the readme section is the usual way.

The section also documents two requirements that arose from the recent changes and were undocumented as well. Facts
have to be gathered, because the package names, the trust store anchor and the update command are resolved by
distribution, os_family and architecture. And the role needs become, since it writes into /etc and updates the trust
store.

No version is pinned. All used modules exist since community.crypto 1.0.0, so a lower bound would be arbitrary.

Co-authored-by: Copilot <copilot@github.com>
2026-09-07 22:30:59 +02:00

5 lines
43 B
YAML

---
collections:
- name: community.crypto