4032dea6d2
Support the composes/<id>/manifests API endpoint for non-koji builds. The endpoint will have to anyway handle `osbuild` job results once Koji composes will start using `osbuild` job type for builds. The endpoint previously contained a bug. If the `osbuild-koji` job had an empty manifest attached as a static job argument (this is the default type value), then this empty manifest was added to the endpoint response. Since Cloud API uses the depsolve and manifest jobs, the actual manifest was never attached to the job as a static argument. As a result, the endpoint was always returning an empty manifest for any koji compose. Fixing this required also adjusting unit tests, which was relying on the buggy behavior. Extend the unit test testing a successful compose to test the logs endpoint. |
||
|---|---|---|
| .. | ||
| errors.go | ||
| errors_test.go | ||
| handler.go | ||
| openapi.v2.gen.go | ||
| openapi.v2.yml | ||
| server.go | ||
| v2_internal_test.go | ||
| v2_koji_test.go | ||
| v2_multi_tenancy_test.go | ||
| v2_test.go | ||