Bug 1042973 - [RFE][oslo]: Advanced validation of config options
Summary: [RFE][oslo]: Advanced validation of config options
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Upstream M2
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/oslo...
Whiteboard: upstream_milestone_icehouse-2 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 16:49 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-27 13:49:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-13 16:49:58 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/oslo-config-options-validation.

Description:

Currently  it is possible to specify the data types of config options. Each option class (IntOpt, FloatOpt, etc) defines a converter function, which transforms strings read from config files to values of target data types. Though, it's up to developers to check, that these values are actually eligible (e. g. an int value is within some predefined range). It would be very useful, to have such validators directly in oslo.config

Specification URL (additional information):

None
Comment 2 Stephen Gordon 2014-01-23 20:50:55 UTC 
Moving to POST based on upstream status (Implemented).
Note You need to log in before you can comment on or make changes to this bug.