•  
     
    story #6422 uploaded files via REST
Summary
Empty
uploaded files via REST
Empty
  • New Routes
  1. /api/v1/artifact_files/ (OPTIONS, POST)
  2. /api/v1/artifact_files/:ifileId (OPTIONS, GET, PATCH, DELETE)
  • Additional info for
  1. /api/v1/artifacts/:id (PUT, GET)
  • Documentation on how to manipulate a file via REST
  • see https://tuleap.net/wiki/index.php?pagename=RESt%20API&group_id=101#Attachments for details
  • Garbage collector to remove uploaded files not associated to an artifact after a time period (7 days)
  • Limit the number of files/ data uploaded per user per day (see SOAP)
  • Temporary storage until file is associated to artifact
  • User uploads first chunk via POST then subsequent chunks via PATCH
  • POST returns ID to use via PATCH

 

 

Empty
Empty
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
#6422
dylan bowden (dylan)
2014-03-28 17:29
2014-03-11 14:23
6494

References
Referencing story #6422
Referenced by story #6422

Artifact

art #6479

Follow-ups

User avatar
dylan bowden (dylan)2014-03-12 11:15
  • 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
dylan bowden (dylan)2014-03-12 11:08
  • 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
  • Permissions set to