Story #5251
closed
Dependency Downloading for Ansible Collection sync
Status:
CLOSED - DUPLICATE
Description
Ticket moved to GitHub: "pulp/pulp_ansible/685":https://github.com/pulp/pulp_ansible/issues/685
Dependency Downloading when syncing collections:¶
When syncing a collection, we would like to have the collections listed as dependencies to be synced into the repository as well.
Example: https://docs.ansible.com/ansible/devel/dev_guide/collections_galaxy_meta.html#examples
For a collection to be synced, having the below dependencies:
dependencies:
"other_namespace.collection1": ">=1.0.0"
"other_namespace.collection2": ">=2.0.0,<3.0.0"
"anderson55.my_collection": "*" # note: "*" selects the highest version available
The 3 listed collections should also get synced when syncing the collection.
Can the user disable this as an option? I'm hoping so. What would the option be called sync_dependencies? Is there a better name? Also does it default to on or off?
I think making it optional is fine, and defaulting to off is fine too!
Regarding name. What's the option called when copying content over in pulp_rpm with dependencies?
Let's definitely discuss. This was an open item to discuss later, but I thought we were going with an include/exclude list rather than dependency solving for the initial feature.
- Subject changed from Dependency Solving for Ansible Collection sync to Dependency Downloading for Ansible Collection sync
- Description updated (diff)
This should be called 'Dependency Downloading' instead of 'Dependency Solving'.
bmbouter - thanks for the clarification. Understanding that other Ansible software also supports strict enforcement of dependencies being available was helpful. Sounds like this tracker covers just recursive_conservative and only for downloading/sync and not repo copy use case. My main concern was scope and effort involved (as dependency solving for all cases in RPM connotes a very large effort.) I now understand that this functionality would keep this behavior consistent with Ansible Automation Hub and a better experience for the end user without requiring efforts similar to RPM "depsolving" or being inconsistent with Ansible treatment of dependencies.
rchan wrote:
bmbouter - thanks for the clarification. Understanding that other Ansible software also supports strict enforcement of dependencies being available was helpful. Sounds like this tracker covers just recursive_conservative and only for downloading/sync and not repo copy use case. My main concern was scope and effort involved (as dependency solving for all cases in RPM connotes a very large effort.) I now understand that this functionality would keep this behavior consistent with Ansible Automation Hub and a better experience for the end user without requiring efforts similar to RPM "depsolving" or being inconsistent with Ansible treatment of dependencies.
This makes sense with the language I was using (the RPM language). Thanks for asking and following up.
- Tags Katello added
- Tags deleted (
Katello-P2)
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Also available in: Atom
PDF
.