We actually changed this on purpose for 6.1 to turn of pagination by default:
https://bugzilla.redhat.com/show_bug.cgi?id=1190857
the side effect is that some API calls can return a *lot* of data.
For 6.2 we can investigate a few options:
* Timing functions where hammer will indicate the call is taking a while and possibly returning lots of data. give the user a suggestion to CTRL+C and use the --per-page option
* Have APIs offer a default pagination with the requirement to use a param to indicate you want *all* results

After https://github.com/theforeman/hammer-cli/pull/174 you can add a default option for pagination. You can even scope it to a specific resourse. I think it will cover both cases - if a user wants, he can add a pagination option, and the global default is full results.
Is it a valid workaround?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501

Note

You need to
log in
before you can comment on or make changes to this bug.