File Service Needs Staging Storage Container
File service currently puts all files into opendes container. Upcoming changes to file service require a staging storage container to store files in temporarily before being moved into the persistent storage container that we now have. This has a number of benefits
- When generating signed URLs for users, they will only have write access to the staging container and only have read access to the persistent storage.
- The current workflow is that the client uploads the data to the staging container, calls the API to update the metadata to reflect the changes in persistent store. However, the signed url will have an expiry of seven days which means that the client can update the file even after the metadata is updated. This could result in inconsistencies between the content and the metadata.
Acceptance Criteria:
- Staging storage container added