-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose batch_qs() to the plugin API #4607
Comments
closes pulp#4607 pulp_deb has a use case for finding the duplicates, but then needs to perform additional processing to decide whether to actually remove them or not. This change splits a find_duplicates function out from remove_duplicates to facilitate this.
closes pulp#4607 pulp_deb has a use case for finding the duplicates, but then needs to perform additional processing to decide whether to actually remove them or not. This change splits a find_duplicates function out from remove_duplicates to facilitate this.
Ok, so my request may have been premature, the draft PR I added would allow me to reuse more pulpcore code than exposing |
The approach from my draft PR turned out to be a complete dead end, so I am back to needing |
If there are no concerns, I would like to have
batch_qs
from https://github.com/pulp/pulpcore/blob/main/pulpcore/app/util.py#L182Made available to plugins here: https://github.com/pulp/pulpcore/blob/main/pulpcore/plugin/util.py#L15
The reason, is that I need this helper function to fix pulp/pulp_deb#921 and I would prefer not to duplicate it.
See also: https://discourse.pulpproject.org/t/exposing-new-things-to-the-plugin-api/1021
Note: I am fine with duplicating the pulpcore function for any pulp_deb backports, and switching to the pulpcore version with whatever pulpcore release first exposes it. So there is no need to backport the pulpcore change anywhere.
The text was updated successfully, but these errors were encountered: