Project

Profile

Help

Task #3337

When publishing a file repo, if two content units have the same path, only the latest content unit should be published

Added by daviddavis about 2 years ago. Updated 3 months ago.

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

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Target Release - File:
Sprint:
Sprint 32

Description

Suppose I upload two different files to a file repository but both have the same relative_path (e.g. "test.iso"). Both will be attached to the repository. The file publisher should only use the latest one when creating the publication.

Associated revisions

Revision a15d800d View on GitHub
Added by jortel@redhat.com about 2 years ago

Publish newest content when dup paths exist. closes #3337

History

#1 Updated by jortel@redhat.com about 2 years ago

  • Sprint/Milestone set to 54
  • Groomed changed from No to Yes

#2 Updated by jortel@redhat.com about 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to jortel@redhat.com

#4 Updated by jortel@redhat.com about 2 years ago

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

#5 Updated by bmbouter almost 2 years ago

  • Sprint set to Sprint 32

#6 Updated by bmbouter almost 2 years ago

  • Sprint/Milestone deleted (54)

#7 Updated by bmbouter 10 months ago

  • Tags deleted (Pulp 3, Pulp 3 MVP)

#8 Updated by bmbouter 3 months ago

  • Sprint/Milestone set to 0.1.0

#9 Updated by bmbouter 3 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF