-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
builder: use cloud api #73
Conversation
cb580ce
to
f83ef48
Compare
Composer PR landed, this is ready for review. |
Reading through this, I realised we may not have enabled all the necessary image types in the cloud api in composer? And the names of some will have changed, where should we do the backwards compatible translation? In the koji plugin? |
By looking at openapi.v2.yml I think we at least miss
I think it makes sense to have it here, maybe switch the over in Pungi and then remove the translation layer later here. |
That would be perfect I think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Composer now[1] has integrated the koji API into the "cloud API" and thus we can use this more general purpose and powerful API instead of using the specialized koji API endpoint. Adapt the request and response structures as well as the unit tests to use that. [1] PR #2214, commit 11e2ae45284bfb0d89ef1c1e0d2aa4ae230ea573
Take the current list of valid image types currently supported by the cloud api and validdate it during the compose request. Also allow a test "image_type" image type which is used all over the place in the testing code.
Map the image types used by the koji API to the image types used by the cloud api. This should allow for a smooth transition when the plugin is upgraded, i.e. the pungi configuration can be used unmodified. After all the plugins are upgraded the pungi config should be changed to use the native image types and then this mapping could be removed again.
Update composer to a commit that includes the new integrated cloud API as well as exposing all the image types via it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! I have one non-blocking question...
I just double checked that we get a new In method we get the handler class (
and then a new instance is invoked:
matching our case |
Port the plugin to use the Composer's cloud API.
Needs osbuild/osbuild-composer#2214