CLI commands "repos/products enable/disable" do too much but do not catch wrong user input about rmt HOT 5 CLOSED

IIRC, repos enable 123 and product enable 123 do different things: the former enables a repo with ID 123, the latter enables a product with ID 123. Both also accept the product/version/arch product string.

How to do it better is open for discussion, of course. Some user testing/other 3rd-party input would be nice. Let's ping @kalabiyau for starters 😬

from rmt.

@ikapelyukhin I am planning a card where we will work with internal customers to see their feedback on usability. As well, there are plans to reach out to real customers and to see what do they think. For now, I believe we could live with simplest solution and improve it as we learn from users.

from rmt.

@kalabiyau as a real customer using rmt, we're OK so long as it's clearly documented. If maintaining better code means rmt-cli repos/product enable repo/product id is the best way, then that's fine by us. Initial setup of rmt-server is so simple, picking the repo/product number from the list seems trivial to us, especially if the --help and man pages explain this.

from rmt.

@thutterer I think that we will keep the product id and string for the foreseeable future, as rmt-cli products enable sles/15 will enable all architectures and a product id does not.

With the updates to rmt-cli products enable, do you still see the need to do something or can we close this?

from rmt.

@thutterer can I close this issue?

from rmt.