No description
Upstream composer has introduce a few changes that we need to adapt for: - the koji composer API is now exposed on the standard https port (443). Thus koji hub and web need to move to a different pair: 8080 (http) and 4343 (https). Change the scripts and tests for that - the koji API gained a prefix 'api/composer-koji/v1/'. Change client and unit tests to use that prefix. Use urljoin to create new APIs - composer configuration format (osbuild-composer.toml) has changed and now also includes configuration for the CA and allowed domains - update the composer RPM repositories to the commit for the 21 upstream release. |
||
|---|---|---|
| .github | ||
| container | ||
| plugins | ||
| schutzbot | ||
| test | ||
| .editorconfig | ||
| .gitignore | ||
| .pylintrc | ||
| HACKING.md | ||
| koji-osbuild.spec.in | ||
| LICENSE | ||
| make-tags.sh | ||
| meson.build | ||
| meson_options.txt | ||
| README.md | ||
| run-builder.sh | ||
| run-koji-container.sh | ||
| run-tests.sh | ||
Koji osbuild
This project provides osbuild integration with Koji. This is done via three plugins:
- Koji hub plugin: Provides a new XMLRPC API endpoint that clients
can use to create new
osbuildImageKoji tasks. - Koji builder plugin: Handles
osbuildImageKoji tasks and will talk to osbuild-composer to create new composes via composer's Koji API. - Koji cli plugin: Adds a new
osbuild-commandto the existingkojicommand line client. This will then use the new XMLRPC API to request a new compose.
Development
See HACKING.md for how to develop and test this project.