Project

Profile

Help

Issue #9544

Define API to serve ContentSignatures

Added by rochacbruno about 1 month ago. Updated 4 days ago.

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/

{
"signatures": [
    ... all the signatures present for that specif content version or artifact
]
}

The exact design of that API serializer is TBD


Related issues

Blocked by Pulp - Issue #9543: Define and Create a Model to store Content SignaturesCLOSED - DUPLICATE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by rochacbruno about 1 month ago

  • Description updated (diff)

#2 Updated by rochacbruno about 1 month ago

  • Blocked by Issue #9543: Define and Create a Model to store Content Signatures added

#3 Updated by gerrod 4 days ago

  • Status changed from NEW to CLOSED - DUPLICATE

Please register to edit this issue

Also available in: Atom PDF