Actions
Task #4034
closed
Use the pass_through option when generating new publications
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
We just added a new pass_through option to publications. Since PublishedArtifacts have the same path as their respective content artifacts, I think it's safe to have the publishing code just create pass_through publications and remove the use of PublishedArtifacts. This will save time and reduce the number of records in the database.
Related issues
Updated by daviddavis over 5 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Updated by daviddavis over 5 years ago
- Blocked by Story #4020: Extend Content App to serve Artifacts from ContentArtifact.relative_path data associated w/ the repo_version associated with the publication added
Added by ppicka over 5 years ago
Updated by ppicka over 5 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset a3da01a9f1be528e0f428857a1cd7e2157b6baa9.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Use pass_through publications
Use only pass_through pulbications to avoid creating PublishedArtifact db entry and use new feature of pulp.
closes: #4034
Signed-off-by: Pavel Picka ppicka@redhat.com