Currently, there are only POST and DELETE endpoints for registering/indexing and removing objects, respectively. However, this presents a user from choosing their own identifier during registration and also makes it impossible to update any given object. While DRS objects are generally meant to be permanent, and so updating an object is not required, in some situations, e.g., when registering objects that are inherently temporary, such functionality would be desirable.
Proposed solution
[ ] Add a PUT /objects/{object_id} endpoint to the DRS-Filer custom OpenAPI specification here; an example for a PUT endpoint definition can be found in the TRS-Filer repository
[ ] Modify the existing controller for POST /objects so that it supports PUTting objects as well; an example for how the same controller is used for both POSTing and PUTting resources can be found in the TRS-Filer repository
Description
Currently, there are only
POSTandDELETEendpoints for registering/indexing and removing objects, respectively. However, this presents a user from choosing their own identifier during registration and also makes it impossible to update any given object. While DRS objects are generally meant to be permanent, and so updating an object is not required, in some situations, e.g., when registering objects that are inherently temporary, such functionality would be desirable.Proposed solution
PUT /objects/{object_id}endpoint to the DRS-Filer custom OpenAPI specification here; an example for aPUTendpoint definition can be found in the TRS-Filer repositoryPOST /objectsso that it supportsPUTting objects as well; an example for how the same controller is used for bothPOSTing andPUTting resources can be found in the TRS-Filer repository