Issue #3881
closed
FileDownloader Destroys my Data
Description
Problem¶
If you use file:// as your protocol handler with a remote.feed Pulp will move your file into the backend. If you have a backup of your published data, you probably don't want it destroying the original copy.
Solution¶
The FileDownloader should save a copy of the data into the working directory just like the HttpDownloader does. This will cause the data to be copied and the original source left alone. Then when being moved into the backend it will already be on the same filesystem for the final move.
Updated by CodeHeeler over 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 40
Updated by jortel@redhat.com over 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
Updated by jortel@redhat.com over 5 years ago
bmbouter: I use file:/// urls all the time when testing the File pluign and have not observed the behavior you've described. What am I missing?
Updated by bmbouter over 5 years ago
- Status changed from ASSIGNED to CLOSED - NOTABUG
I tried to reproduce this locally with the latest pulp_file and a local PULP_MANIFEST repo. I couldn't reproduce it like I was before. I think this has to be closed NOTABUG so I'm doing that now.
@jortel thank you for looking into this, and also for asking me to test it again also. Sorry it took me so long to get around to it.
.