Actions
Story #5431
closed
Story #5112: [Epic] As a user, I can manage auxiliary content types
Story #5429: As a user, I can manage custom repository metadata
As a user, I can sync custom repository metadata
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 59
Quarter:
Description
All custom (unknown to Pulp) repository metadata is synced to Pulp.
There can be only one custom repository metadata of a certain type in a repository version.
(Currently it should be handled by RemoveDuplicates stage, later it will be a repo_key feature)
Store file as an Artifact. Relative path in ContentArtifact os not used, so it can be anything there (data_type?)
Updated by daviddavis about 5 years ago
This story doesn't mention it but I assume we need to store the file as an Artifact. What value do we store in the relative path for the content artifact?
Updated by daviddavis about 5 years ago
- Groomed changed from No to Yes
- Sprint set to Sprint 58
Updated by fao89 about 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
Updated by fao89 about 5 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar about 5 years ago
Updated by Anonymous about 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset e0df34a641a48a91568d3ea1894f5625671fdc05.
Updated by ttereshc almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Syncing custom/unknown repository metadata
closes #5431 https://pulp.plan.io/issues/5431 Required PR: https://github.com/pulp/pulp_rpm/pull/1438