Actions
Issue #9544
closed
Define API to serve ContentSignatures
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Related to https://pulp.plan.io/issues/9543
Story: As a client consuming a content, I want to be able to fetch all the signatures related to a specific content in order to perform verification prior to installation.
e.g:
GET /pulp/signatures/<content-artifact-identification>
{
"signatures": [
... all the signatures present for that specif content version or artifact
]
}
The exact design of that API serializer is TBD
Related issues
Updated by rochacbruno about 3 years ago
- Blocked by Issue #9543: Define and Create a Model to store Content Signatures added
Updated by gerrod almost 3 years ago
- Status changed from NEW to CLOSED - DUPLICATE
Actions
.