There were no tests that show what happens when you create or
update the 'enabled' field in endpoints with different types of
values. There were also no tests that show what happens when the
'enabled' field isn't specified when an endpoint is created.
The new tests show that you can set the 'enabled' field to
any type of value even though the identity API specification says
that it's a Boolean. The new tests also show that if the 'enabled'
field isn't set explicitly then it's not returned on the response.
Reviewed: https:/ /review. openstack. org/77038 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=ad5a7a1d274 c3c6b2051850b9c f1b5979d069570
Committed: https:/
Submitter: Jenkins
Branch: master
commit ad5a7a1d274c3c6 b2051850b9cf1b5 979d069570
Author: Brant Knudson <email address hidden>
Date: Thu Feb 27 19:16:02 2014 -0600
Add tests for endpoint enabled.
There were no tests that show what happens when you create or
update the 'enabled' field in endpoints with different types of
values. There were also no tests that show what happens when the
'enabled' field isn't specified when an endpoint is created.
The new tests show that you can set the 'enabled' field to
any type of value even though the identity API specification says
that it's a Boolean. The new tests also show that if the 'enabled'
field isn't set explicitly then it's not returned on the response.
Change-Id: Iadc2a0ed3d6aaa a89b82f4caa8829 ecd1d8f2712
Related-Bug: #1282266