f96a661ada
* Add a toggle to control the number of signatures required to verify the authenticity of a collection * Make the default number of required valid signatures 1 * Add option to make signature verification strict and fail if there are no valid signatures (e.g. "+1") * Use a regex to validate --required-valid-signature-count * Add a toggle to limit the gpg status codes that are considered a failure * Update documentation and changelog * Add unit and integration tests for the new options * Fixes #77146 Fix using user-provided signatures when running 'ansible-galaxy collection verify ns.coll --offline' Add a test for a user-provided signature when running ansible-galaxy collection verify with --offline Fix displaying overall gpg failure without extra verbosity Add a test for displaying gpg failure without verbosity Improve documentation to be more clear that signature verification only currently applies to collections directly sourced from Galaxy servers |
3 years ago | |
|---|---|---|
| .. | ||
| .templates | 3 years ago | |
| _static/css | 4 years ago | |
| rst | 3 years ago | |
| sphinx_conf | 3 years ago | |
| .gitignore | ||
| .nojekyll | ||
| Makefile | 3 years ago | |
| Makefile.sphinx | ||
| README.md | 3 years ago | |
| ansible_2_5.inv | ||
| ansible_2_6.inv | ||
| ansible_2_7.inv | ||
| ansible_2_8.inv | 4 years ago | |
| ansible_2_9.inv | ||
| ansible_2_10.inv | 4 years ago | |
| ansible_3.inv | 4 years ago | |
| ansible_4.inv | 3 years ago | |
| ansible_5.inv | 3 years ago | |
| collection-plugins.yml | 4 years ago | |
| jinja2.inv | 4 years ago | |
| known_good_reqs.txt | 3 years ago | |
| modules.js | ||
| python2.inv | ||
| python3.inv | 3 years ago | |
| requirements.txt | 3 years ago | |
| variables.dot | ||
README.md
Ansible documentation
This project hosts the source behind the general pages of docs.ansible.com. Module-specific documentation is hosted in the various collections repositories. See Ansible Galaxy, the list of Ansible-maintained collections, and the ansible-collections organization for collections sources.
To create clear, concise, and consistent contributions to Ansible documentation, please refer to the following information.
Contributions
Contributions to the documentation are welcome.
The Ansible community produces guidance on contributions, building documentation, and submitting pull requests, which you can find in Contributing to the Ansible Documentation.
You can also join the Docs Working Group and/or the #ansible-docs IRC channel on irc.libera.chat
Ansible style guide
Ansible documentation is written in ReStructuredText(RST). The Ansible style guide provides linguistic direction and technical guidelines for working with reStructuredText, in addition to other resources.
Tools
The Ansible community uses a range of tools and programs for working with Ansible documentation. Learn more about Other Tools and Programs in the Ansible Community Guide.
GitHub
Ansible documentation is hosted on the Ansible GitHub project and various collection repositories, especially those in the ansible-collections organization. For general GitHub workflows and other information, see the GitHub Guides.