security group rule create doesn't allow protocol-less rules

[IWAMOTO Toshihiro]

$ openstack security group rule create --help

  --protocol <protocol>
                        IP protocol (ah, dccp, egp, esp, gre, icmp, igmp,
                        ipv6-encap, ipv6-frag, ipv6-icmp, ipv6-nonxt,
                        ipv6-opts, ipv6-route, ospf, pgm, rsvp, sctp, tcp,
                        udp, udplite, vrrp and integer representations
                        [0-255]; default: tcp)

A SG rule's protocol field is optional and can be left unspecified.
However, the CLI doesn't allow such a rule.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/512113

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/512113
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=82f45d9bd203aee77914c1f9e300f7dbedf673c8
Submitter: Zuul
Branch: master

commit 82f45d9bd203aee77914c1f9e300f7dbedf673c8
Author: Daniel Speichert <email address hidden>
Date: Sun Oct 15 16:35:37 2017 -0400

    Allow creating security rules without protocol

    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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-openstackclient 3.13.0 release.