[Pulp-list] Puppet in the CLI

Ashley Penney apenney at gmail.com
Wed Aug 22 12:50:36 UTC 2012


I prefer this new option, I think.  It's straightforward and keeps a
single binary for interaction.  It sets out what kind of data you are
using right from the start and makes that very clear.  It works for
me!

On Wed, Aug 22, 2012 at 8:41 AM, Jay Dobies <jason.dobies at redhat.com> wrote:
> On 08/22/2012 02:43 AM, Jason Connor wrote:
>>
>> I'm also leaning toward option 2, version 2.
>>
>> I tried mental exercise on a 3rd version. Namely and auto-type detecting
>> script, but you hung up on the help flag alone, so I don't think it'll fly.
>>
>> O2V2 is, imo, the cleanest.
>
>
> I thought of a O2V2 this morning where we keep a single pulp-admin script
> but branch at the root of the commands:
>
> pulp-admin rpm repo ...
> pulp-admin puppet repo ...
> pulp-admin generic repo ...
>
> It's basically the same concept of individual trees of commands, but a
> single script. I'm still leaning towards O2V2, but figured I'd throw that
> out there.
>
>
>> Jason L Connor
>> linear on freenode #pulp
>> http://pulpproject.org/
>> RHCE: 805010912355231
>> GPG Fingerprint: 2048R/CC4ED7C1
>>
>>
>>
>> On Aug 21, 2012, at 9:40 AM, Jay Dobies <jason.dobies at redhat.com> wrote:
>>
>>> https://fedorahosted.org/pulp/wiki/GCCLITypes
>>>
>>> When first adding the RPM extensions, I knew we'd have to figure
>>> something out when we supported Puppet but decided to hold off on the
>>> decision and see how things took shape.
>>>
>>> It's time to revisit the CLI structure and how to handle the fact that
>>> the Pulp team is now providing support for 2 different plugin packs, keeping
>>> in mind that that number may grow depending on what other types of content
>>> we decide to bite off and maintain as a team (or get contributed).
>>>
>>> The page above describes my thought process in how to handle our admin
>>> CLI with multiple types. I included some chat conversations with the
>>> community on what they think as well.
>>>
>>> It's pretty clear reading it which way I'm leaning. I'd like to come to a
>>> conclusion following the scrum meeting tomorrow, but I don't want to wait
>>> that long to hear any brilliant ideas you have on the issue since I'll
>>> probably start down a path this afternoon. So please reply to this or me
>>> personally if you have a strong opinion in any direction.
>>>
>>> --
>>> Jay Dobies
>>> Freenode: jdob @ #pulp
>>> http://pulpproject.org | http://blog.pulpproject.org
>>>
>>> _______________________________________________
>>> Pulp-list mailing list
>>> Pulp-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
>>
>
>
> --
> Jay Dobies
> Freenode: jdob @ #pulp
> http://pulpproject.org | http://blog.pulpproject.org
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list




More information about the Pulp-list mailing list