ansible-galaxy collection install dep resolver changes

[jborean93]

SUMMARY

The current dep resolver for ansible-galaxy collection install does 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 (--force-with-deps for dep conflicts) is required. The --force argument has it's own problem and acts like a sledgehammer removing all the collections and starting again. To prepare for adding the --upgrade flag to install we first need to fix this behaviour. The following changes need to be made to how the dep resolver works

• When a version constraint is specified that does not match an already installed collection, update it
  • Current behaviour requires --force
• When a dep constraint does not match an already installed collection, update it
  • Current behaviour requires --force-with-deps

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.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

ansible-galaxy collection install

ADDITIONAL INFORMATION

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.

[jborean93]

ansible/proposals#181 (comment) also sums up the proposed end goal for the new dep resolver.

[jborean93]

Was implemented with #72591 and subsequently followed up with #73336.