/ ansible Public
ansible-galaxy collection install dep resolver changes #71784
This issue/PR relates to a feature request.
This issue has an associated PR.
This issue/PR relates to code supported by the Ansible Engineering Team.
The current dep resolver for
ansible-galaxy collection installdoes not handle updating of collections too well. The current behaviour will never upgrade an already installed collection even if a newer one was available. If a version constraint was specified that the current collection does not meet then it will error saying
--force-with-depsfor dep conflicts) is required. The
--forceargument has it's own problem and acts like a sledgehammer removing all the collections and starting again. To prepare for adding the
installwe first need to fix this behaviour. The following changes need to be made to how the dep resolver works
The relevant tests will need to be updated and an integration test added for these 2 scenario changes. The _build_dependency_map function is a good starting point for this.
ansible-galaxy collection install
The new dep resolver behaviour is planned to act like
pip. Some test scenarios for pip can be found at https://gist.github.com/jborean93/65495d1e36aa9c02fbdf707d4232fff7.
The text was updated successfully, but these errors were encountered: