XML endpoint client use correct string for enabled
The XML endpoint client was passing enabled='True' or
enabled='False' when creating or updating an endpoint.
The Keystone XML parser expects 'true' and 'false' for the
'enabled' attribute and only converts those strings to a Boolean
value, other values are passed through as strings.
Note that the XML identity_client correctly converts the Boolean
values to lowercase strings already.
Reviewed: https:/ /review. openstack. org/76949 /git.openstack. org/cgit/ openstack/ tempest/ commit/ ?id=3340299e055 4c8b07d07bfbeb4 7dee45d47d3ab2
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3340299e0554c8b 07d07bfbeb47dee 45d47d3ab2
Author: Brant Knudson <email address hidden>
Date: Thu Feb 27 13:31:37 2014 -0600
XML endpoint client use correct string for enabled
The XML endpoint client was passing enabled='True' or
enabled='False' when creating or updating an endpoint.
The Keystone XML parser expects 'true' and 'false' for the
'enabled' attribute and only converts those strings to a Boolean
value, other values are passed through as strings.
Note that the XML identity_client correctly converts the Boolean
values to lowercase strings already.
Change-Id: I2f1374430d1869 59aca8fb90b4f77 30044ec0c65
Closes-Bug: #1282266