remove "v1" multipart upload code

Description

"v2" of multipart upload was introduced in an additive sense, allowing gradual migration to the new version. Now that the migration is done we need to remove the original version to avoid having duplicate code. Removal involves a final migration step in which internal usage (e.g. uploads of wikis and zipped file bundles by workers) is migrated to the "v2" code.

Environment

None

Activity

Show:
Ziming Dong
March 4, 2021, 1:44 AM

Resolved in

Ziming Dong
May 29, 2019, 1:36 AM

The only usages of POST /createchunkedfileuploadtoken are from the COMMAND_LINE client as recent as 2 months ago (April 20, 2019).
We should start users who are still using clients that are many years outdated to update.

John Hill
September 11, 2018, 7:33 PM

While working on PLFM-5086, I encountered the deprecated code again. Ran the following query to determine if the "v1" services were still in uses:

DISTINCT P.NORMALIZED_METHOD_SIGNATURE

GET /entity/#/uploaddestination

GET /entity/#/uploaddestinations

GET /file/#

GET /file/bulk/async/get/#

GET /file/bulk/async/start

GET /filehandle/#

GET /filehandle/#/url

POST /externalfilehandle

POST /file/bulk/async/start

POST /file/multipart

POST /file/multipart/#/presigned/url/batch

POST /filehandle/batch

PUT /file/multipart/#/add/#

PUT /file/multipart/#/complete

GET /completeuploaddaemonstatus/#

GET /file/multipart/#/complete

POST /createchunkedfileuploadchunkurl

POST /createchunkedfileuploadtoken

POST /filehandles/copy

POST /startcompleteuploaddaemon

POST /externalfilehandle/proxy

GET /externalfilehandle/proxy

GET /filehandle/batch

GET /externalfilehandle

DELETE /filehandle/#

These results indicate that the 'v1' services are still in use

Duplicate

Assignee

Ziming Dong

Reporter

Bruce Hoff

Validator

Bruce Hoff

Priority

Minor

Labels

None

Development Area

None

Sprint

None

Fix versions

Release Version History

None

Story Points

None

Epic Link

None

Slack Channel

None