Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
One usability complaint against subscription-manager are all of the difficult to read command line options that are composed of multiple words (e.g. --servicelevel) These can be improved by inserting a dash between the words (e.g. --service-level).
Beware: As many command line options are changed, a few other updates also need to be made...
bash-completion
man pages
a deprecated warning when attempting to use the former option should be printed to stderr, but still pass through and execute the command
Version-Release number of selected component (if applicable):
[root@jsefler-7 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.26-1
subscription management rules: 5.11
subscription-manager: 1.13.3-1.el7
python-rhsm: 1.13.2.1-2.el7
How reproducible:
Steps to Reproduce:
After going through the CLI --help messages, I found all of these options that could be improved...
Actual results:
--proxyuser=PROXY_USER
--proxypassword=PROXY_PASSWORD
--serverurl=SERVER_URL
--serverurl=SERVERURL
--ondate=ON_DATE
--autoheal
-s SERVICELEVEL, --servicelevel=SERVICELEVEL
--servicelevel=SERVICE_LEVEL
--listslots
--listhooks
--activationkey=ACTIVATION_KEYS
--consumerid=SYSTEMID
--name=SYSTEMNAME
--type=UNITTYPE
--baseurl=BASE_URL
Expected results:
--proxy-user=PROXY_USER
--proxy-password=PROXY_PASSWORD
--server-url=SERVER_URL
--server-url=SERVER_URL
--on-date=ON_DATE
--auto-heal
-s SERVICE_LEVEL, --service-level=SERVICE_LEVEL
--service-level=SERVICE_LEVEL
--list-slots
--list-hooks
--activation-key=ACTIVATION_KEYS
--consumer-id=SYSTEMID
--name=SYSTEM-NAME
--type=UNIT_TYPE
--base-url=BASE_URL
On second thought, the "baseurl" option is well understood and used in yum repo definitions. I feel "baseurl" should remain as-is with no hyphen inserted.
After some discussion, it seems likely that changing all of the commands at this point would cause more problems than it would solve. As such, existing commands will not be changed.
https://github.com/candlepin/subscription-manager/pull/1045