Reviewed: https://review.openstack.org/395736 Committed: https://git.openstack.org/cgit/openstack/cliff/commit/?id=a89dbbb2fe305656e8b3ed60a5273ff8f50bb233 Submitter: Jenkins Branch: master
commit a89dbbb2fe305656e8b3ed60a5273ff8f50bb233 Author: Steve Martinelli <email address hidden> Date: Wed Nov 9 12:28:04 2016 -0500
Replace dashes and colons when using bash formatter
When a resource property has dashes and colons and the bash formatter is used, it actually breaks with `command not found`.
For example, when doing: eval `osc network show public --format shell`
The network resource has a property: provider:network_type="vxlan"
Which results in: "bash: provider:network_type=vxlan: command not found"
Change-Id: I57ca08c9dfd7ef022ab91d50ec42a98a6df08b09 Closes-Bug: #1616323
Reviewed: https:/ /review. openstack. org/395736 /git.openstack. org/cgit/ openstack/ cliff/commit/ ?id=a89dbbb2fe3 05656e8b3ed60a5 273ff8f50bb233
Committed: https:/
Submitter: Jenkins
Branch: master
commit a89dbbb2fe30565 6e8b3ed60a5273f f8f50bb233
Author: Steve Martinelli <email address hidden>
Date: Wed Nov 9 12:28:04 2016 -0500
Replace dashes and colons when using bash formatter
When a resource property has dashes and colons and
the bash formatter is used, it actually breaks with
`command not found`.
For example, when doing:
eval `osc network show public --format shell`
The network resource has a property: network_ type="vxlan"
provider:
Which results in: network_ type=vxlan: command not found"
"bash: provider:
Change-Id: I57ca08c9dfd7ef 022ab91d50ec42a 98a6df08b09
Closes-Bug: #1616323