Bug #18340

Hammer params for ordering are inconsistent

Added by Tomáš Strachota 6 months ago. Updated 6 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:Other commands
Target version:Foreman - Team Marek backlog
Difficulty: Bugzilla link:1417726
Found in release: Pull request:
Story points-
Velocity based estimate-

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1417726

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):
hammer-cli-foreman 0.9.0
hammer-cli-katello 0.3.0

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.


Related issues

Blocked by Katello - Bug #18341: API sort hash is not working, but sort_by and sort_order ... New 02/01/2017

History

#1 Updated by Tomáš Strachota 6 months ago

  • Subject changed from Hammer params for ordering are inconsistent to Hammer params for ordering are inconsistent
  • Description updated (diff)
  • Target version set to Team Marek backlog

#2 Updated by Tomáš Strachota 6 months ago

  • Blocked by Bug #18341: API sort hash is not working, but sort_by and sort_order are working but undocumented added

Also available in: Atom PDF