Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Currently, there are many commands in hammer cli that return extremely generic help messages which do not actually help, or do not specify required options of a given command
Version-Release number of selected component (if applicable):
6.1.9
How reproducible:
100%
Steps to Reproduce:
One example would be:
hammer> content-view create
Could not create the content view:
Error: Could not find organization, please set one of options --organization, --organization-label, --organization-id.
hammer> content-view create -h
Usage:
content-view create [OPTIONS]
Options:
--component-ids COMPONENT_IDS List of component content view version ids for composite views
Comma separated list of values.
--composite Create a composite content view
--description DESCRIPTION Description for the content view
--label LABEL Content view label
--name NAME Name of the content view
--organization ORGANIZATION_NAME Organization name to search by
--organization-id ORGANIZATION_ID organization ID
--organization-label ORGANIZATION_LABEL Organization label to search by
--repositories REPOSITORY_NAMES Comma separated list of values.
--repository-ids REPOSITORY_IDS repository ID
Comma separated list of values.
-h, --help print help
hammer>
--organization, --organization-label, --organization-id should have descriptions that let the user know they are required to use the command.
--repositories should let us know that (truly) we need this to have a real, functional content-view.
The same situation applies to --composite and its relationship to --component-ids.
We basically need an overview of all help texts for hammer cli, or we need to link detailed documentation in this help output if we are going to choose to be blatantly non-specific.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: Currently, there are many commands in hammer cli that return extremely generic help messages which do not actually help, or do not specify required options of a given command Version-Release number of selected component (if applicable): 6.1.9 How reproducible: 100% Steps to Reproduce: One example would be: hammer> content-view create Could not create the content view: Error: Could not find organization, please set one of options --organization, --organization-label, --organization-id. hammer> content-view create -h Usage: content-view create [OPTIONS] Options: --component-ids COMPONENT_IDS List of component content view version ids for composite views Comma separated list of values. --composite Create a composite content view --description DESCRIPTION Description for the content view --label LABEL Content view label --name NAME Name of the content view --organization ORGANIZATION_NAME Organization name to search by --organization-id ORGANIZATION_ID organization ID --organization-label ORGANIZATION_LABEL Organization label to search by --repositories REPOSITORY_NAMES Comma separated list of values. --repository-ids REPOSITORY_IDS repository ID Comma separated list of values. -h, --help print help hammer> --organization, --organization-label, --organization-id should have descriptions that let the user know they are required to use the command. --repositories should let us know that (truly) we need this to have a real, functional content-view. The same situation applies to --composite and its relationship to --component-ids. We basically need an overview of all help texts for hammer cli, or we need to link detailed documentation in this help output if we are going to choose to be blatantly non-specific.