yahoo-eng-team team mailing list archive

[Dolph Mathews <1255585@xxxxxxxxxxxxxxxxxx>]

This is, as you noted, out of scope for keystoneclient to fix.. unless
we were going to switch from argparse which is unlikely. This shortcut
behavior is by design in argparse; related discussion here:

  http://bugs.python.org/issue14910

** Changed in: keystone
       Status: New => Invalid

** Also affects: python-keystoneclient
   Importance: Undecided
       Status: New

** No longer affects: keystone

** Changed in: python-keystoneclient
       Status: New => Invalid

** Bug watch added: Python Roundup #14910
   http://bugs.python.org/issue14910

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1255585

Title:
  Incorrect parameters are being considered in case it is a prefix of an
  existent

Status in Python client library for Keystone:
  Invalid

Bug description:
  
  When keystone is called with an invalid parameter (p1) which is prefix of valid one (p2) , it is happening that there are not errors triggered and the parameter p2 is used with the value set for p1.

  This is an example:

  The service-create command is waiting for a --name parameter as is
  shown in this example

  ------------------------------------------------------------------------------------------------
  >keystone service-create --name=test2 --type=identity --description="test"

  +-------------+----------------------------------+
  |   Property    |              Value                                  |
  +-------------+----------------------------------+
  | description |               test                                   |
  |      id              | 11dfdc75e10e4d2d96ed1c14361ccfdf |
  |     name        |              test2                                  |
  |     type          |             identity                               |
  +-------------+----------------------------------+
  ------------------------------------------------------------------------------------------------

  A now I call with the parameter --na instead of --name, and the value
  is used for the service name

  ------------------------------------------------------------------------------------------------
  >keystone service-create --na=test3 --type=identity --description="test"

  +-------------+----------------------------------+
  |   Property    |              Value                                   |
  +-------------+----------------------------------+
  | description |               test                                   |
  |      id              | 6f0bc993d7b146d9a85e818338115c57 |
  |     name        |              test3                                  |
  |     type          |             identity                               |
  +-------------+----------------------------------+
  ------------------------------------------------------------------------------------------------

  This doesn't happen in case I call with names instead of name.

  The same issue happen with other commands in keystone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-keystoneclient/+bug/1255585/+subscriptions