Clarification Needed: Setting up Koji-OSBuild with Local Build Configuration

[lemingg]

I am currently working on setting up Koji-OSBuild for creating installation ISOs from my local Koji packages. I have been going through the documentation on GitHub, but I find it a bit insufficient for my understanding, especially when it comes to configuring the connection between Koji and osbuild-composer.

My primary goal is to use the Koji CLI to input a command that will build an installation ISO using my local Koji packages. However, I am a bit confused about the involvement of the cloud in the process, as described in the documentation. For my specific use case, I only require a local build and do not need any cloud-based services.

Could you please provide some guidance on the following points?

How to properly configure the connection between Koji and osbuild-composer for a local build?
Is it possible to use Koji-OSBuild without involving any cloud services? If yes, could you please provide some insights on how to achieve this?
Are there any specific configurations or settings that I need to be aware of while setting up Koji-OSBuild for a local build?
Any help, detailed explanations, or examples of configuration files would be greatly appreciated.

Thank you for your time and assistance.

[supakeen]

For the direct question, @thozza do you have thoughts? I'm not sure if koji-osbuild can be configured to speak to a local API. Browsing its code makes it seem that the endpoint is configurable but there is also a bunch of SSO things in there that might make it hard.

For an indirect answer: we are planning to provide a different entry level to build images through koji which will land in koji-osbuild in hopefully the near future and should simplify all these service things (but that's not something of use to you right now).

[thozza]

My suggestion would be to have a look at our integration test in https://github.com/osbuild/koji-osbuild/blob/main/test/integration.sh.

The Koji plugin should be able to speak to a local API endpoint, but you will need to "fake" the SSO. For the second part, you can use a dummy implementation that is used in integration test.