[katello-devel] Content view filters cli usages

[Justin Sherrill]

On 02/01/2013 07:52 AM, David Davis wrote:
> I hope I'm not derailing this but since I am working on the rest of the CLI (other than filters), I was wondering if I should modify the arguments' names to be consistent with how filters is planned to work. I know we brought this up yesterday but I figured it might also help to have others' input--especially since this is uncharted territory with new subcommands.
>
> For reference, this is how it's currently set up:
>
> katello content definition update --name=def1 --new_name=def1new
> katello content definition update --label=def2 --new_name=def2new
> katello content definition update --id=3 --name_name=newone
> katello content definition publish --name=def3 --view_name=def3view1
> katello content definition publish --label=def4 --view_name=def4new
>
> Based on this format that you're using:
>
> katello content definition filter list --org="ACME" --definition="content_def"
>
> Should I change my commands to something like this?
>
> katello content definition update --definition=def1 --new_name=def1new
> katello content definition update --definition_label=def2 --new_name=def2new
> katello content definition update --definition_id=3 --name_name=newone
> katello content definition publish --definition=def3 --view_name=def3view1
> katello content definition publish --definition_label=def4 --view_name=def4new
+1 to this (not using --name)

> Thank you.
>
> David
>
> ----- Original Message -----
>> From: "Partha Aji"<paji at redhat.com>
>> To: katello-devel at redhat.com
>> Sent: Thursday, January 31, 2013 6:37:48 PM
>> Subject: [katello-devel] Content view filters cli usages
>>
>> After some discussions with a few folks i have updated the content
>> view filters wiki page with various cli usages (this is not
>> implemented but more of a preview)
>>
>> https://fedorahosted.org/katello/wiki/ContentViewFilters
>>
>> Opening it up for discussions.
>>
>> In coming up with a rule definition i needed 2 basic criteria met
>> 1) User must be able to set multiple<package name, operator,
>> version>  tuples in one line.
>> 2) User must be able to specify version ranges for a particular
>> package. For example foo*,<2.8,>  2.6
>>
>>
>> I m open for suggestions if you have a simpler way to represent the
>> usages presented..
>>
>> Partha
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
>>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel