debian-forge-composer/internal
Ondřej Budai b64bbaa0bb api/jobqueue: move build id to url
Imho it makes more sense from REST perspective. Also, in the future there
will be ROUTE for uploading image to image build. As it's not a good idea
transport file inside JSON, all the parameters (compose id and image
build id) need to be inside the URL. Therefore for the sake of consistency,
all these routes should have compose id and image build id in the URL.

There is another solution to embedding multiple values inside http body
which allows file transport - multipart/form-data. I think using form-data
is worth when doing more complex stuff, for our usecase transporting all
the metadata in the URL is more appropriate solution.
2020-02-14 11:53:38 +01:00
..
blueprint blueprints: fix group handling 2019-12-17 09:24:15 +01:00
common common: refactor build states into a separate file 2020-02-12 11:17:26 +01:00
compose drop the Compose.Image field 2020-02-14 11:53:38 +01:00
crypt crypt: make it possible to compile and test on macOS 2020-01-30 14:42:25 +01:00
distro distro: remove previous implementation of testing distro 2020-02-12 11:17:26 +01:00
jobqueue api/jobqueue: move build id to url 2020-02-14 11:53:38 +01:00
mocks/rpmmd Weldr API: use the new compose/store API 2020-02-12 11:17:26 +01:00
pipeline distro: add custom image size 2020-01-23 00:57:31 +01:00
rcm RCM API: return bad request instead of internal server error 2020-02-12 11:17:26 +01:00
rpmmd repositories: install the base repositories in the filesystem 2020-01-03 22:35:52 +01:00
store drop the Compose.Image field 2020-02-14 11:53:38 +01:00
target target: use the new types from common package 2020-02-12 11:17:26 +01:00
test api: implement /compose/log 2019-12-20 11:43:39 +01:00
upload upload/aws: Add basic S3 upload test 2020-01-16 13:14:15 +01:00
weldr drop the Compose.Image field 2020-02-14 11:53:38 +01:00