ansible

Commit Graph

Author	SHA1	Message	Date
Sloane Hertel	f96a661ada	ansible-galaxy - add configuration options for more flexible collection signature verification (#77026 ) * 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
Sloane Hertel	43e55db208	ansible-galaxy - add signature verification of the MANIFEST.json (#76681 ) * ansible-galaxy collection install\|verify: - Support verifying the origin of the MANIFEST.json when the Galaxy server has provided signatures. - Allow supplemental signatures to use during verification on the CLI/requirements file. * ansible-galaxy collection install: - Support disabling signature verification. This silences the warning provided by ansible-galaxy if the Galaxy server provided signatures it cannot use because no keyring is configured. - Store Galaxy server metadata alongside installed collections for provenance. This is used by 'ansible-galaxy collection verify --offline'. * Add unit tests for method that gets signatures from a Galaxy server * Add integration tests for user-provided signature sources - Test CLI option combinations - Test installing collections with valid/invalid signature sources - Test disabling GPG verification when installing collections - Test verifying collections with valid/invalid signature sources * Make signature verification advisory-by-default if signatures are provided by the Galaxy server - Make the default keyring None - Warn if the keyring is None but the Galaxy server provided signatures - Error if the keyring is None but the user supplied signatures - Error if the keyring is not None but is invalid * changelog * add ansible-galaxy user documentation for new options Co-authored-by: Matt Martz <matt@sivel.net> Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua> Co-authored-by: Martin Krizek <martin.krizek@gmail.com> Co-authored-by: Sandra McCann <samccann@redhat.com> Co-authored-by: Andy Mott <amott@redhat.com> Co-authored-by: John R Barker <john@johnrbarker.com>	3 years ago
Daniel Goldman	be2bd2f1af	Documentation for other types in collection `requirements.yml` (#75872 )	3 years ago
Alicia Cozine	0e9d1ab1cc	incorporate minimalism feedback on distributing collections page (#75266 )	3 years ago
Sloane Hertel	e40889e711	Add support to install collections from git repositories (#69154 ) * Enable installing collections from git repositories * Add tests for installing individual and multiple collections from git repositories * Test to make sure recursive dependencies with different syntax are deduplicated * Add documentation * add a changelog * Skip Python 2.6 * Only fail if no collections are located in a git repository Add support for a 'type' key for collections in requirement.yml files. Update the changelog and document the supported keys and allowed values for the type. Add a note that the collection(s) in the repo must contain a galaxy.yml * Add a warning about embedding credentials in SCM URLs * Update with review suggestions * suppress sanity compile failure for Python 2.6	5 years ago
Jordan Borean	ecea15c508	Unify ansible-galaxy install -r (#67843 ) * Unify ansible-galaxy install -r * Minor nit fixes for docs * Re-align warnings * Fix up integration test * Fix up test where no roles/collections were in file	5 years ago
Jake Jackson	d60b17082e	small fix to install command as no longer needs -p by default (#68947 )	5 years ago
Sam Doran	6c70959131	Update example requirements file docs (#67626 ) Use "name" when possible rather than "src" to make the examples of roles and collections in a single requirements files more coherenant. Fundamentally, roles and collections are completely different. But we can make the requiremets file easier to read by unifying the format as much as possible.	5 years ago
Sandra McCann	5eceebcaf3	Clarify how to install roles and collections from same requirements file (#65707 )	5 years ago
Sandra McCann	ae265bc546	Move galaxy appendix info to a new Galaxy section (#63356 ) * start galaxy docs restructure * shared snippets in txt files * moved all content to galaxy section	5 years ago

10 Commits (201aba3d0f6801471a3f9ef66eff2b7cc0d77b97)