Data inconsistency between output with Hammer-Katello-Cli

Hello All,

I've been working on a bug recently dealing with the way that Hammer
outputs data. For reference here is the link to the bug:
Bug #12267: Inconsistent output on hammer repository-set - Hammer CLI - Foreman The problem is when telling it
to give the output normally the last column 'enabled' is in yes or no
format. It is this way because when the command was created in
hammer-cli-katello it was given the Boolean formatter. When the same query
is output in csv format it shows up as true or false because it is not run
through any of the formatters defined in the orignal command. I have heard
different opinions on this topic and was wanting to hear from others about
it as well.

So far some of the opinions have been that CSV format should be more
computer readable so filtering true/false to yes/no is undesirable. Another
point though is that there should be a way for a consumer to get uniform
data each time data is printed out.

Thanks all!

>
> Hello All,
>
> I've been working on a bug recently dealing with the way that Hammer
> outputs data. For reference here is the link to the bug:
> Bug #12267: Inconsistent output on hammer repository-set - Hammer CLI - Foreman The problem is when telling
> it to give the output normally the last column 'enabled' is in yes or no
> format. It is this way because when the command was created in
> hammer-cli-katello it was given the Boolean formatter. When the same query
> is output in csv format it shows up as true or false because it is not run
> through any of the formatters defined in the orignal command. I have heard
> different opinions on this topic and was wanting to hear from others about
> it as well.
>
> So far some of the opinions have been that CSV format should be more
> computer readable so filtering true/false to yes/no is undesirable. Another
> point though is that there should be a way for a consumer to get uniform
> data each time data is printed out.
>

As the reporter of this bug, it's this latter point that is key. The data
that is returned should be uniform and consistent irrespective of the
output format specified (and other subcommands should also utilise the same
out value - either true / false or yes / no.

ยทยทยท On Saturday, March 5, 2016 at 1:32:14 AM UTC-5, zhun...@redhat.com wrote:

Thanks all!