Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #12322 have git-lfs batch and basic transfer API
Summary
Empty
have git-lfs batch and basic transfer API
Empty

Overview

At this step, it's not meant to be used in production yet. Feature is hidden behind a feature flag.

This is the first story to have basic git lfs support that means

  • Only HTTPS support (ssh will come after)
  • Basic auth for transfers
  • No locks

The implementation is done outside restler, using front router.

Technical overview

POST https://tuleap.example.com/plugins/git/projectname/foo/bar.git/info/lfs/objects/batch

Check API reference. Implement the upload, download and verify actions. Permission for actions regarding to 'ref' are used. API rely on basic auth.

The batch upload "reserve" the object place temporarly (stored in DB) to ensure consistency between batch and PUT.

[PUT|GET] https://tuleap.example.com/plugins/gitlfs

Check API reference. Implement the data transfer (download & upload)

Note: the implementation need to check and ensure

  • What authorizations are needed between batch and transfert API
  • Storage: use flysystem to abstract storage means

The files are purged on project deletion.

There is not global reference counting at this time.

 

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
#12322
Manuel Vacelet (vaceletm)
2018-12-05 08:38
2018-09-25 15:09
4255

References
Referencing story #12322

Artifact

epic #11511 Git LFS
rel #12269 10.8
story #12323 have git-lfs lock API
story #12324 use git-lfs with ssh transfer
request #17102 Git LFS Objects from deleted repositories are not removed
Display settings

Follow-ups

User avatar
Thomas Gerbet (tgerbet)2018-11-20 13:49
Storage of Git LFS objects is going to be done at the instance level to allow for de-duplication of objects between repositories of the whole instance.
  • 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
Manuel Vacelet (vaceletm)2018-09-28 15:46
  • 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
Manuel Vacelet (vaceletm)2018-09-25 15:23
  • 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
Manuel Vacelet (vaceletm)2018-09-25 15:22
  • 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