Project

Profile

Help

Task #5430

Story #5112: [Epic] As a user, I can manage auxiliary content types

Story #5429: As a user, I can manage custom repository metadata

Add a content model and a serilaizer for custom repository metadata

Added by ttereshc about 1 year ago. Updated 10 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 59
Quarter:

Description

Fields:
data_type
checksum (of a file, just to be able to notice two same content units at the content save time)

Custom metadata is stored in a file as an Artifact.

Suggested name of a model: RepoMetadataFile

Associated revisions

Revision f1f757f1 View on GitHub
Added by Fabricio Aguiar about 1 year ago

Adding RepoMetadataFile model.

closes #5430 https://pulp.plan.io/issues/5430

History

#1 Updated by daviddavis about 1 year ago

What should the model name be?

#2 Updated by ttereshc about 1 year ago

  • Description updated (diff)

#3 Updated by daviddavis about 1 year ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 58

#4 Updated by fao89 about 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89

#5 Updated by fao89 about 1 year ago

  • Status changed from ASSIGNED to POST

#6 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 58 to Sprint 59

#7 Updated by Anonymous about 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#8 Updated by ttereshc 10 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF