•  
     
    story #12813 upload files with FRS REST API
Summary
Empty
upload files with FRS REST API
Empty

Leveraging what was done for docman REST api, upload will be done following tus.io protocol.

POST /frs_files
{
  "release_id": int,
  "name": "string",
  "file_size": int
}

On success, POST will return a href where client can push content using tus.io protocol.

PUT /upload/files/:reference
Empty
Nouha Terzi (terzino), Denis PILAT (denis_pilat)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12813
Manuel Vacelet (vaceletm)
2019-03-19 17:10
2019-01-23 12:16
4158

References

Follow-ups

User avatar
The POSTĀ representation has been taken from the existing representation of a file. However, we decide to remove properties that are not mandatory to create a file in order to ease the development of this story, and to not let the consumer in the wild (eg. what are acceptable values for arch or type?).

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Deletion is done in dedicated story #13022

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • CC list set to Denis PILAT (denis_pilat), Nouha Terzi (terzino)