-
Notifications
You must be signed in to change notification settings - Fork 108
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
composer-cli has a poor user experience #1105
Comments
Agreed. Thoughts on this @bcl ? |
The referenced BZ number looks like an easy fix on the composer-cli side and there is existing test suite which can easily handle the described scenario.
This sounds like a separate issue from what I can understand. If that's the case it needs to be recorded and tracked separately.
This will cause some disruption of the existing CI but is definitely doable and makes sense.
This is a completely different ball game and QE objects to that! It needs to be vetted via the appropriate channels and make sure the internal cli client is adequately tested and matches functionality in existing composer-cli, etc. This is a lot more work than it looks like on the surface. |
@atodorov you are right, I mixed two issues into one, but given that I don't know either of them is a priority for us, I thought it would make a case for overtaking composer-cli under osbuild organization. I, of course, understand that a complete rewrite will come with regressions for some users so I see the reason to object, but suppose this is something we would like to do in a long run. Do you have a suggestion for best path forward? Would it be possible to hook QE tests for composer-cli to osbuild-composer repo? |
For both splitting up the composer-cli component from the lorax repo and/or complete replacement with a different cli client (which means rebase/obsolete of the existing RPM) you should start with a formal RHBZ request so we can plan for deadlines, priority and resources.
Everything is possible, it's source code after all. The cli test suite is bash script + beakerlib so it is fairly portable. That said the devil is always in the implementation details and the issues that we discover along the way. |
One more related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1915353 |
@bcl is working on this |
There have been 2 reported complaints about the composer-cli usability:
Real world example:
I'm reporting this issue here because I think that
osbuild
organization should take the ownership ofcomposer-cli
and possibly use the golang client we already have in/internal/client
.The text was updated successfully, but these errors were encountered: