This contribution introduces in Tuleap a way to parse batch requests according to the specification [0]. In order to do that, the Git HTTP operations are extended to support the Batch URL POST /objects/batch. The support is for now incomplete and partially incorrect: * nothing is implement besides the request parsing so no batch reponse will be provided * authorization verification is not implemented * responses are supposed to be in the Git responses format, most errors that might be thrown are not. To support that cleanly, some changes need to be introduced in the ways Tuleap handles errors and responses. You can trigger the implemented HTTP route by crafting a valid request on a repository accessible by anonymous users. On success, the parsed batch request will be dumped in the git_syslog. For example, with curl: $ curl -X POST -H 'Accept: application/vnd.git-lfs+json' \ 'https://tuleap.example.com/plugins/git/projectname/reponame.git/info/lfs/objects/batch' \ --data \ '{"operation": "download", "transfers": [ "basic" ], "ref": { "name": "refs/heads/master" }, "objects": [{"oid": "12345678", "size": 123}]}' Git LFS HTTP routes are only accessible when an undocumented feature flag ('git_lfs_dev_enable') is enabled until a minimal support of the Git LFS workflow is implemented. This is part of story #12322: have git-lfs batch and basic transfer API [0] https://github.com/git-lfs/git-lfs/blob/v2.6.0/docs/api/batch.md Change-Id: I9fdeb2ee84532b4244ad6a5f8e020db613cedb93

+1050 −54

Author

Thomas Gerbet (tgerbet) 2018-11-14 17:51

Committer

Manuel Vacelet (vaceletm) 2018-11-15 11:28

Hash d25e076c5050bfd6a099d5248b2122f021c0b5ce

Parent ac3532c4e62491eedadd9a530b0281c3bd2fa204

Reference git #tuleap/stable/d25e076c5050bfd6a099d5248b2122f021c0b5ce