2860398c2a
Yes. This goes against my desire not to change code to accommodate tests. But there is no other good way to test compose results without long running, and possibly fragile, composes. And this matches lorax's behavior. The change adds support for the ?test=1|2 query parameter to the compose POST, and a new store function - PushTestCompose that handles creating the fake compose results. Passing ?test=1 will create a failed compose. Passing ?test=2 will create a successful compose, but one without any files. The purpose of these is to be able to test the compose result API responses like compose/failed, etc. |
||
|---|---|---|
| .. | ||
| api.go | ||
| api_test.go | ||
| compose.go | ||
| json.go | ||
| upload.go | ||
| util.go | ||