Bug 1417726

Summary: Hammer params for ordering are inconsistent
Product: Red Hat Satellite Reporter: Tomas Strachota <tstrachota>
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.3CC: dhlavacd, jcallaha, mhulan, swadeley, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 17:43:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1309791    

Description Tomas Strachota 2017-01-30 18:41:57 UTC 
Description of problem:

Foreman part of hammer cli uses parameter --order="<FIELD_NAME> <DIRECTION>" for ordering results. Katello part uses two parameters --by="<FIELD_NAME>" and --order="<DIRECTION>"

For example compare
> hammer architecture list -h
and
> hammer repository list -h


Apart from the above there are additional issues:
* in Katello commands --by and --order seem to have no effect (probably related to bz 1138262)
* in Foreman commands there's no validation of the direction and API silently falls back to 'ASC'


Version-Release number of selected component (if applicable):
Satellite 6.2.3


Actual results:
There are various parameters for ordering results, some of the dysfunctional.


Expected results:
Hammer should provide unified commands for ordering fields. Probably only --order should be used.
Comment 2 Tomas Strachota 2017-02-01 12:48:48 UTC 
Created redmine issue http://projects.theforeman.org/issues/18340 from this bug
Comment 3 Bryan Kearney 2018-09-04 17:43:21 UTC 
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.