ansible

Commit Graph

Author	SHA1	Message	Date
Sviatoslav Sydorenko	7662a05085	Always allow "no-other-choice" pre-release dependencies when resolving collection dependency tree PR #81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit `6f4b4c345b`, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref #73416 Ref #79112 Fixes #79168 Fixes #80048 Resolves #81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com>	1 year ago
Matt Martz	92d5ffda82	Update galaxy_ng container for tests (#80721 )	2 years ago
Wong Hoi Sing Edison	016b7f71b1	ansible-galaxy - support `resolvelib >= 0.5.3, < 1.1.0` (#80196 ) * ansible-galaxy - support `resolvelib >= 0.5.3, < 1.1.0` <https://pypi.org/project/resolvelib/1.0.1> released on 2023-03-09: - <https://github.com/sarugaku/resolvelib/blob/main/CHANGELOG.rst#101-2023-03-09> - <https://github.com/sarugaku/resolvelib/releases/tag/1.0.1> Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com> * Trigger CI by pinning resolvelib with latest version Since resolvelib is pre-installed in our test containers, we should temporarily pin the latest version allowed to force the tests to run with that version. Once the tests have passed that commit can be reverted. Please make those changes without force pushing, so that we keep the reference to the passing CI run. We can squash the commits when merging the PR so the temporary commits won't be in the final commit merged to the devel branch. Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com> * https://github.com/ansible/ansible/pull/80196#discussion_r1136003637 Also test resolvelib with multiple supported versions. Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com> * Revert "Trigger CI by pinning resolvelib with latest version" This reverts commit `5518e5dbca`. --------- Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>	2 years ago
Sloane Hertel	a02e22e902	Add --offline option to 'ansible-galaxy collection install' (#78678 ) * Add --offline option to 'ansible-galaxy collection install' to prevent querying distribution servers This allows installing/upgrading individual tarfiles to have dependency resolution. Previously needed to be done manually with --no-deps or else all collections and dependencies needed to be included in the requirements. Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>	2 years ago
Sloane Hertel	143e7fb45e	ansible-galaxy - support resolvelib versions >= 0.5.3, < 0.9.0 (#77649 ) * ansible-galaxy - support resolvelib versions >= 0.5.3, <= 0.8.1 Test incompatibilities are removed for resolvelib >= 0.6.0 Test against the latest 0.8.x version and fix requirements * Fix tests - use a venv for testing the range of resolvelib versions * Update temporary hardcoded fallback for ansible-test * Update hardcoded upperbound for sanity tests * Make error check more flexible	3 years ago
Sloane Hertel	82f3a57bee	Fix ansible-galaxy traceback when unexpected version of resolvelib is installed (#77630 ) * Fix traceback when a supported version of resolvelib is not installed Try to read the supported version range from the package distribution info and fall back to a hardcoded lowerbound/upperbound (>=0.5.3,<0.6.0). * Add tests for unsupported resolvelib versions * Resolve remaining import sanity test issues. Co-authored-by: Matt Clay <matt@mystile.com> Co-authored-by: Matt Martz <matt@sivel.net>	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	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
Sviatoslav Sydorenko	6f4b4c345b	Match user-requested transitive pre-releases in collection dependency resolver (#73416 ) * Add direct+transitive pre-release regression test * Match user-requested transitive pre-releases This change makes sure that in scenario when a user requests collectionA-pre and collectionB that depends on collectionA, collectionA-pre would actually match that collectionA requirement while `--pre` is unset. Co-authored-by: Jordan Borean <jborean93@gmail.com>	4 years ago
Sloane Hertel	0a60e5e341	Add a couple more tests to ansible-galaxy-collection (#72931 ) * Test installing a dependency compatible with multiple collection requirements Test downloading a collection without dependencies * Move cleanup to the end of the test suite	4 years ago
Jordan Borean	fb092a82a1	ansible-galaxy - source deps from all servers and not just parent (#72576 ) * ansible-galaxy - source deps from all servers and not just parent * Added integration tests for this scenario	4 years ago
Jordan Borean	de5858f48d	Added caching mechanism for Galaxy API requests (#71904 ) * Added caching mechanism for Galaxy API requests * Add cache options and split up code * Added unit tests * Fix sanity test * Use modified date and fix up caching for explicit servers * Make sure credentials are not in cached server name * Added test for getting updated cache version * Changes from review	4 years ago
Matt Martz	ce570691e7	Test against galaxy_ng (#70303 ) * Test against galaxy_ng * Switch container image * Remove redundant \|default * Re-enable * Update image * Update wording * Don't use pulp as the container name	5 years ago
Matt Martz	b748edea45	Add multipart/form-data functionality (#69376 ) * Add multipart/form-data functionality * Fix some linting issues * Fix error message * Allow filename to be provided with content * Add integration test * Update examples * General improvements to multipart handling * Use prepare_multipart for galaxy collection publish * Properly account for py2 vs py3, ensuring no max header length * Address test assumptions * Add unit tests * Add changelog * Ensure to use CRLF instead of NL * Ignore line-endings in fixture * Consolidate code, add comment * Bump fallaxy container version * ci_complete	5 years ago

14 Commits (6c0f4c8a2df78e0863723bffa06f6594b9bdd540)