Project

Profile

Help

Actions
Send by e-mail Copy link

Task #3337

closed

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

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

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
jortel@redhat.com
Sprint/Milestone:
0.1.0
Start date:
Due date:
% Done:

100%

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

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.

Actions
Copy link
 #1

Updated by jortel@redhat.com almost 7 years ago

  • Sprint/Milestone set to 54
  • Groomed changed from No to Yes
Actions
Copy link
 #2

Updated by jortel@redhat.com almost 7 years ago

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

Added by jortel@redhat.com almost 7 years ago

Revision a15d800d | View on GitHub

Publish newest content when dup paths exist. closes #3337

Actions
Copy link
 #4

Updated by jortel@redhat.com almost 7 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by bmbouter almost 7 years ago

  • Sprint set to Sprint 32
Actions
Copy link
 #6

Updated by bmbouter almost 7 years ago

  • Sprint/Milestone deleted (54)
Actions
Copy link
 #7

Updated by bmbouter over 5 years ago

  • Tags deleted (Pulp 3, Pulp 3 MVP)
Actions
Copy link
 #8

Updated by bmbouter about 5 years ago

  • Sprint/Milestone set to 0.1.0
Actions
Copy link
 #9

Updated by bmbouter about 5 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF