-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a user, I want to force an upload of file that is already in S3 or the Registry #100
Comments
from the breakout meeting today: file name/path We are not sure yet what the best key should provided by the API, either: option1: node + file path β returns md5sum, lidvid With option 1, a new end-point for the API could be: /files/{node}/{file_path} which would return the {md5sum}Β The issue is that the file_path is not always the same, on the staging bucket or where the file is archived eventually.Β @ramesh-maddegoda, @viviant100 could you investigate how the path on the archive bucket (ODR) is being created from the path in the staging bucket ? |
Waiting for Jordan for validation |
Validated with endpoint /files/{md5sum} to be developed in the API. |
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Node Operator
πͺ Motivation
...so that I can overwrite data that has already been loaded into the PDC
π Additional Details
No response
Acceptance Criteria
Given a file that has already been loaded into the registry
When I perform a DUM upload with the
--overwrite
flag enabledThen I expect the data to overwrite the existing file in the system, and DUM to note that this occurred in the logs
βοΈ Engineering Details
No response
The text was updated successfully, but these errors were encountered: