Add endpoints related to temporary file management#301
Merged
Conversation
…ke them temporary.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds four endpoints that allow us to manage temporary files that are stored in our database. The temporary nature of these database items is handled via a procedure on the backend.
The new endpoints are:
POST /temp- Accepts the file contents asmultipart/form-data. Information about the file's expiration time, detected MIME type, and the URL from which its contents can be retrieved are given in both the response body and the headersPATCH /temp/<uuid>- Allows modifying the content of the specified file. To keep things simple, we enforce that the MIME type stay constantGET /temp/<uuid>- Returns the contents of the temporary fileDELETE /temp/<uuid>- If necessary, a temporary file can be manually deleted