-
Notifications
You must be signed in to change notification settings - Fork 79
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
Filters for exploring Content relationships #646
Labels
Comments
PR filed as #647 |
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
Nov 9, 2022
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
Dec 8, 2022
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
Jan 31, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
Apr 26, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
Apr 28, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
May 11, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
May 11, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
May 17, 2023
sdherr
added a commit
to sdherr/pulp_deb
that referenced
this issue
May 17, 2023
quba42
added a commit
that referenced
this issue
Jun 1, 2023
#646: Add filters to select by related pulp_deb content types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pulp_deb
allows users to configure apt releases/distros, components, and what packages go in them by allowing users to addReleases
,ReleaseComponents
,PackageReleaseComponents
, andPackages
, all of which are types of genericpulpcore
Content and all of which get mapped to a particularRepositoryVersion
. That's fine, exceptpulp_deb
is missing all filters that allow you to explore more than one link in that relationship tree.So for example if I wanted to answer the question "What Packages are currently in this Release", I'd have to:
We can and should create some filters in
pulp_deb
that allow you to simply ask the question and get the answer. Converting this to a single db query would be a much more efficient and user-friendly way to solve the problem. I have a code change to supply these filters that is currently being tested, Pull Request incoming shortly.The text was updated successfully, but these errors were encountered: