Story #1836
closedApplicability query should return unit keys instead of object ids
0%
Description
Using the command below, I am querying the API for errata that are applicable to consumer c1:
http -a admin:admin --verify=no POST https://localhost/pulp/api/v2/consumers/content/applicability/ < content_app_query.json
content_app_query.json looks like this:
{
"criteria": {
"filters": {"id": {"$in": ["c1"]}}
},
"content_types": ["erratum"]
}
The API returns:
[
{
"applicability": {
"erratum": [
"b3472b1f-1d68-4f48-bded-d26aee03dc38"
]
},
"consumers": [
"c1"
]
}
]
However, when I want to use the API to install content on a consumer, I need to provide the unit key which in this case is the errata_id:
"errata_id" : "RHEA-2012:0055",
I suspect that the applicability querying API should return the unit keys instead of object ids.
Updated by dkliban@redhat.com almost 8 years ago
After some discussion with Justin from Katello, I have determined that the change I proposed is backwards incompatible. Katello uses object ids to query Pulp for full errata documents to store in Katello's database.
Updated by dkliban@redhat.com almost 8 years ago
- Tracker changed from Issue to Story
- Subject changed from Applicability query returns unit object ids instead of unit key to Applicability query should return unit keys instead of object ids
- Groomed set to No
- Sprint Candidate set to No
Updated by bmbouter almost 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.