2ceffb3796
Modify the Koji image extra metadata to not depend on the upload target data structures for upload results. The target results are supposed to be specific to the uploader implementation, which will eventually change. Moreover, the definition is internal to osbuild-composer, so this would create a problem once the Koji upload implementation is moved to osbuild/images. The Koji upload implementation does not really care about the exact structure of the upload results. It is just a list of JSON objects. Signed-off-by: Tomáš Hozza <thozza@redhat.com> |
||
|---|---|---|
| .. | ||
| gen-manifests | ||
| mock-dnf-json | ||
| osbuild-auth-tests | ||
| osbuild-composer | ||
| osbuild-composer-cli-tests | ||
| osbuild-composer-dbjobqueue-tests | ||
| osbuild-dnf-json-tests | ||
| osbuild-image-tests | ||
| osbuild-koji | ||
| osbuild-koji-tests | ||
| osbuild-mock-openid-provider | ||
| osbuild-service-maintenance | ||
| osbuild-store-dump | ||
| osbuild-upload-aws | ||
| osbuild-upload-azure | ||
| osbuild-upload-container | ||
| osbuild-upload-gcp | ||
| osbuild-upload-generic-s3 | ||
| osbuild-upload-oci | ||
| osbuild-upload-pulp-ostree | ||
| osbuild-worker | ||
| osbuild-worker-executor | ||
| README | ||
Binaries ======== osbuild-composer: The main binary, the service that maintains the queue and schedules all jobs. This is started as the main process by systemd or container runtime. osbuild-worker: The worker binary that handles jobs from the job queue locally. osbuild-worker-executor: The binary that runs osbuild to build an image on an isolated VM. osbuild-koji: Submits builds to Koji. Service binaries ================ osbuild-service-maintenance: Vacuum the database and remove old jobs. Also used to cleanup cloud instances. Development and test tools ========================== gen-manifests mock-dnf-json osbuild-auth-tests osbuild-composer-cli-tests osbuild-composer-dbjobqueue-tests osbuild-dnf-json-tests osbuild-image-tests osbuild-koji-tests osbuild-mock-openid-provider osbuild-upload-* osbuild-store-dump: the output from this is used in Test_upgrade in internal/store/json_test.go