From 481018d35410feccb1a219d2028870595dd34656 Mon Sep 17 00:00:00 2001
From: Khyati Sheth <khysheth@ebaysf.com>
Date: Wed, 5 Mar 2014 18:29:20 -0800
Subject: [PATCH] Remove Min/Max for Configuration Group Booleans

boolean configuration-group parameters at the moment require a
min/max value of 0/1 to work around some faulty logic that is
meant to validate integer values, but instead validates integer
and boolean values.

Closes-Bug: #1288507
Change-Id: I2d7556621e891b22291c7ef9e9c523e1ce98a047
---
 trove/configuration/service.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/trove/configuration/service.py b/trove/configuration/service.py
index 891b07307f..df0e249e07 100644
--- a/trove/configuration/service.py
+++ b/trove/configuration/service.py
@@ -198,7 +198,7 @@ class ConfigurationsController(wsgi.Controller):
                 raise exception.UnprocessableEntity(message=msg)
 
             # integer min/max checking
-            if isinstance(v, int):
+            if isinstance(v, int) and not isinstance(v, bool):
                 try:
                     min_value = int(rule.get('min'))
                 except ValueError: