82f45d9bd2
In order to create a rule for any protocol, the client must not specify the protocol in the API call. This is currently impossible because protocol defaults to TCP. In order not to change the default behavior, a "new" protocol name is added: "any", which makes this CLI skip sending the protocol field altogether. Change-Id: I58853d3745f3631007e5e9780c0c5c2526b730a3 Closes-Bug: 1712242
13 lines
435 B
YAML
13 lines
435 B
YAML
---
|
|
features:
|
|
- |
|
|
Add ``any`` as a ``--protocol`` option to ``security group rule create``
|
|
command.
|
|
[Bug `1517134 <https://bugs.launchpad.net/bugs/1712242>`_]
|
|
fixes:
|
|
- |
|
|
It is now possible to create a security rule without specifying protocol
|
|
(using ``--protocol any``), which skips sending the protocol to the API
|
|
server entirely. Previously TCP was forced as default protocol when none
|
|
was specified.
|