ansible

Commit Graph

Author	SHA1	Message	Date
Sandra McCann	7ae1eabaa4	clarify collection signature not available from Community Galaxy (#78386 )	2 years ago
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
Sloane Hertel	bd18be6c0c	Fix ansible-galaxy collection subdir searching and update documentation (#73406 ) * Ensure there is a single source of collection metadata * Allow collection subdirs to be detected by a galaxy.yml or MANIFEST.json * Add documentation about installing and downloading collection directories * Add an example for downloading a git repository * Update documented valid metadata sources for installing git repositories Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua> Co-authored-by: Alicia Cozine <879121+acozine@users.noreply.github.com>	4 years ago
Sloane Hertel	9759e0ca49	add option to upgrade collections (#73336 ) * Add a flag to ansible-galaxy to update collections Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>	4 years ago
Logan Mzz	986c9cf6a1	Docs: Fix collection adjacent folder tree (#66490 ) ##### SUMMARY Previously folder tree example for collection adjacent to the current playbook were displaying a subfolder below the playbook instead of being a sibling.	5 years ago
Sandra McCann	0ca79a4234	Clarify how to use the Galaxy token (#65961 ) * DOCS: clarify how to use the Galaxy token, with info for installs and api-key	5 years ago
Sandra McCann	a01376a493	update configuring ansible-galaxy client (#64796 ) * update configuring ansible-galaxy client, deduplicate, clarify tokens, AH procedures, etc.	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

9 Commits (56f2e65ee78bd0031775e986ff45501b590d9dc1)