Project

Profile

Help

Task #4034

closed

Use the pass_through option when generating new publications

Added by daviddavis about 6 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
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

Blocked by Pulp - Story #4020: Extend Content App to serve Artifacts from ContentArtifact.relative_path data associated w/ the repo_version associated with the publicationCLOSED - CURRENTRELEASEjortel@redhat.com

Actions

Also available in: Atom PDF