Project

Profile

Help

Issue #9544

closed

Define API to serve ContentSignatures

Added by rochacbruno about 1 year ago. Updated about 1 year 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/<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

Blocked by Pulp - Issue #9543: Define and Create a Model to store Content SignaturesCLOSED - DUPLICATEActions
Actions #1

Updated by rochacbruno about 1 year ago

  • Description updated (diff)
Actions #2

Updated by rochacbruno about 1 year ago

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

Updated by gerrod about 1 year ago

  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF