Thanks for the feedback Akihiro
Related to JSON formatting I also find that lbaas pool members shouldn't be
a string but instead it should be a JSON Array.
Could this be something that could be improved?
Thanks!
Ulises
On Fri, Sep 30, 2016 at 1:57 PM, Akihiro Motoki wrote:
> You hit ht
Once the fix is merged, when we specify JSON or other machine readable
format is requested,
neutron CLI does not do any string conversion for data object like array or
dict.
A issue on lbaas pool members will be fixed too.
Akihiro
2016-09-30 21:43 GMT+09:00 Bill Nerenberg :
> Thanks for the feed
You hit https://bugs.launchpad.net/python-neutronclient/+bug/1524624.
The current neutronclient formats an object to string even if non-table
format is specified.
https://review.openstack.org/#/c/255696/ is the fix but it lacks reviewers
for 10 months :(
2016-09-30 18:16 GMT+09:00 Kevin Benton :
Looks very much like a bug (double json encoding). File a bug on launchpad
against python-neutronclient.
On Sep 30, 2016 05:10, "Bill Nerenberg" wrote:
> Hi all
>
> When I run neutron -f json in the command below, the pools value is quoted
> so I cannot use it with JSON parsers like jq
>
> For e
Hi all
When I run neutron -f json in the command below, the pools value is quoted
so I cannot use it with JSON parsers like jq
For example, this is neutron's problematic output [1] (see the pools line)
$ neutron lbaas-loadbalancer-show ef315cff-1d0a-4327-93c6-e9bf7e544e2d -f
json
{
"descriptio
