I did some streamlining of the etherpad on this: https://etherpad.openstack.org/p/MinimalCLI
I agree that required arguments should be positional. The only one that is confusing is the --repo argument to the app create command, which will end up being optional in a subsequent release, so I want to have the CLI use the optional style to begin with for that parameter so it does not need to change later. The aliasing between app and plan is intentional, and is intended with a specific end user type in mind. The cli would work the same if you ran "plan list" and "app list". I also brought the related wiki up to date with this: https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/ApplicationDeploymentAndManagement Adrian On Dec 3, 2013, at 10:29 AM, Russell Bryant <rbry...@redhat.com> wrote: > On 12/03/2013 11:45 AM, Jay Pipes wrote: >> On 12/03/2013 11:39 AM, Arati Mahimane wrote: >>> Randall, I think you are talking about required parameters and we are >>> talking about optional ones. >>> Please correct me if I am wrong. >> >> Russell was specifically talking about required parameters being >> positional arguments. > > Correct. > > Optional still in the form --foo=bar > > -- > Russell Bryant > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
