summaryrefslogtreecommitdiffstats
path: root/openstack/common/plugin
diff options
context:
space:
mode:
authorMark McLoughlin <markmc@redhat.com>2012-07-31 12:16:28 +0100
committerMark McLoughlin <markmc@redhat.com>2012-07-31 12:16:28 +0100
commit038d59778eecf953375da701b4cd55d4e3ca309f (patch)
tree5d0046643bc5c3dcd864675fdac7f09e1c99d0a2 /openstack/common/plugin
parente0134fc3e2d7e59741b3643e2680f578cc9def41 (diff)
downloadoslo-038d59778eecf953375da701b4cd55d4e3ca309f.tar.gz
oslo-038d59778eecf953375da701b4cd55d4e3ca309f.tar.xz
oslo-038d59778eecf953375da701b4cd55d4e3ca309f.zip
Add import_opt() method to ConfigOpts
Related to blueprint cfg-global-object When using the global config object pattern, you often have modules which define options that are referenced in other options. So, for example if module A defined option 'foo' and module be needed to reference that option, you might do: import A print CONF.foo However, this makes it entirely unclear to the casual reader why module A was imported. Nova has a flags.DECLARE() function that helps with this problem by allowing you to do: flags.DECLARE('foo', 'A') The function simply imports module A and checks that the 'foo' option is now defined in the global config object. This is fine, but it is also implicit that this function applies to the global config object. Instead, let's do the following: CONF.import_opt('foo', 'A') Change-Id: I7b98f5be71068bbde70cc0eab991eaebb577de52
Diffstat (limited to 'openstack/common/plugin')
0 files changed, 0 insertions, 0 deletions