Actions
Issue #9543
closed
Define and Create a Model to store Content Signatures
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
Story: Ansible collections and Container Images can be signed using pulp signing services, once a signature is generated we need a place to store the signature along with its metadata.
Signatures are ASCII text blobs or encoded json data
There is no definition yet on how this Model must look like, something that has the following fields.
class ContentSignature(BaseModel | BaseContentType):
signature_artifact: FilePath
# or
signature_blob: Text
metadata: JsonField
content_ptr: (reference to an artifact that can be Collection, Container Image etc)
A content artifact AnsibleCollectionVersion or ContainerImageManifest can have a relationship with one or many signatures
Related issues
Actions
.