The Neutron API dropped XML support quite some time ago. Therefore specifying --request-format xml already produces an error. Even if this parameter is already vestigial and should be abruptly removed. We don't know whether anyone is using it. For instance one could have a set of scripts that explicitly use it just to make sure it never switched without knowing to XML!
Deprecation first is therefore, in my opinion, always the recommended path. Salvatore On 7 December 2015 at 12:58, Akihiro Motoki <[email protected]> wrote: > Hi, > > neutronclient is now dropping XML support and as a result > "--request-format" option is no longer needed as JSON is the only format > now. > > What is the recommended way for options no longer needed? > Does bumping major version of CLI allow us to drop an option without > deprecation? > > - Deprecate such option. > The option still exists with only one available choiceuntil the > option is deleted. > > - Drop it without deprecation. > This breaks users who uses "--requiest-format json", but 'json' is the > default > value and most users do not specify the option. > > Thanks, > Akihiro > > __________________________________________________________________________ > 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
