I'm thinking that the current approach is probably how we want to keep things. I can't imagine many other projects being okay with multiple create calls with the same name. Though if you're really adamant about including that support, we could include a new flag (--or-update) that performs the update if it's found, otherwise it continues with a new create.
Does that make sense? Thanks, Steve Martinelli OpenStack Keystone Core Marek Aufart <[email protected]> wrote on 06/02/2015 10:55:20 AM: > From: Marek Aufart <[email protected]> > To: [email protected] > Date: 06/02/2015 10:55 AM > Subject: [openstack-dev] [openstackclient] Image create-or-update > > Hi, > > I have a question related to openstack image create command v1 from > python-openstackclient. > > It behaves like create-or-update (if image with *name* specified for > create already existed, it is updated). Actually it looks, that it is in > collision with glance, which allows create multiple images with same > names instead of update one. > > Is the create-or-update approach still wanted? > > Related code: > https://github.com/openstack/python-openstackclient/blob/master/ > openstackclient/image/v1/image.py#L247-L269 > > Thanks. > > -- > Marek Aufart > > Email: [email protected] > > IRC: maufart / aufi on freenode > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
