Actions
Story #1836
closedApplicability query should return unit keys instead of object ids
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
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.
Actions