openstack
/
python-openstackclient
Code Issues Proposed changes
python-openstackclient/doc/source/backwards-incompatible.rst

8.2 KiB
Raw Blame History

Backwards Incompatible Changes

Despite our best efforts, sometimes the OpenStackClient team may introduce a backwards incompatible change. For user convenience we are tracking any such changes here (as of the 1.0.0 release).

Should positional arguments for a command need to change, the OpenStackClient team attempts to make the transition as painless as possible. Look for deprecation warnings that indicate the new commands (or options) to use.

List of Backwards Incompatible Changes

  1. Rename command openstack project usage list

The project part of the command was pointless.

  1. <type> should not be optional for command openstack service create

Previously, the command was openstack service create <name> --type <type>, whereas now it is: openstack service create <type> --name <name> This bug also affected python-keystoneclient, and keystone.

  1. Command openstack security group rule delete now requires rule id

Previously, the command was openstack security group rule delete --proto <proto> [--src-ip <ip-address> --dst-port <port-range>] <group>, whereas now it is: openstack security group rule delete <rule>.

  1. Command openstack image create does not update already existing image

Previously, the image create command updated already existing image if it had same name. It disabled possibility to create multiple images with same name and lead to potentially unwanted update of existing images by image create command. Now, update code was moved from create action to set action.

  1. Command openstack network list --dhcp has been removed

The --dhcp option to network list is not a logical use case of listing networks, it lists agents. Another command should be added in the future to provide this functionality. It is highly unlikely anyone uses this feature as we don't support any other agent commands. Use neutron dhcp-agent-list-hosting-net command instead.

  1. Plugin interface change for default API versions

Previously, the default version was set in the parsed arguments, but this makes it impossible to tell what has been passed in at the command line, set in an environment variable or is just the default. Now, the module should have a DEFAULT_API_VERSION that contains the value and it will be set after command line argument, environment and OCC file processing.

  1. image set commands will no longer return the modified resource

Previously, modifying an image would result in the new image being displayed to the user. To keep things consistent with other set commands, we will no longer be showing the modified resource.

  • In favor of: Use set then show
  • As of: NA
  • Removed in: NA
  • Bug: NA
  • Commit: NA
  1. region commands no longer support url

The Keystone team removed support for thr url attribute from the client and server side. Changes to the create, set and list commands for regions have been affected.

  1. flavor set/unset commands will no longer return the modified resource

Previously, modifying a flavor would result in the new flavor being displayed to the user. To keep things consistent with other set/unset commands, we will no longer be showing the modified resource.

  1. security group set commands will no longer return the modified resource

Previously, modifying a security group would result in the new security group being displayed to the user. To keep things consistent with other set commands, we will no longer be showing the modified resource.

  1. compute agent set commands will no longer return the modified resource

Previously, modifying an agent would result in the new agent being displayed to the user. To keep things consistent with other set commands, we will no longer be showing the modified resource.

  1. aggregate set commands will no longer return the modified resource

Previously, modifying an aggregate would result in the new aggregate being displayed to the user. To keep things consistent with other set commands, we will no longer be showing the modified resource.

  1. Output of ip floating list command has changed.

When using Compute v2, the original output of ip floating list command is: +----+--------+------------+----------+-------------+ | ID | Pool | IP | Fixed IP | Instance ID | +----+--------+-----------------------+-------------+ | 1 | public | 172.24.4.1 | None | None | +----+--------+------------+----------+-------------+

Now it changes to: +----+---------------------+------------------+-----------+--------+ | ID | Floating IP Address | Fixed IP Address | Server ID | Pool | +----+---------------------+------------------+-----------+--------+ | 1 | 172.24.4.1 | None | None | public | +----+---------------------+------------------+-----------+--------+

When using Network v2, the output of ip floating list command is: +--------------------------------------+---------------------+------------------+------+ | ID | Floating IP Address | Fixed IP Address | Port | +--------------------------------------+---------------------+------------------+------+ | 1976df86-e66a-4f96-81bd-c6ffee6407f1 | 172.24.4.3 | None | None | +--------------------------------------+---------------------+------------------+------+ which is different from Compute v2.

For Developers

If introducing a backwards incompatible change, then add the tag: BackwardsIncompatibleImpact to your git commit message, and if possible, update this file.

To review all changes that are affected, use the following query:

https://review.openstack.org/#/q/project:openstack/python-openstackclient+AND+message:BackwardsIncompatibleImpact,n,z