<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 24, 2014, at 1:58 PM, Yuriy Taraday <<a href="mailto:yorik.sar@gmail.com">yorik.sar@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 24, 2014 at 4:14 PM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div class="h5"><div>On Jul 23, 2014, at 11:10 PM, Baohua Yang <<a href="mailto:yangbaohua@gmail.com" target="_blank">yangbaohua@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Hi, all<div> The current oslo.cfg module provides an easy way to load name known options/groups from he configuration files.</div><div> I am wondering if there's a possible solution to dynamically load them?</div>
<div><br></div><div> For example, I do not know the group names (section name in the configuration file), but we read the configuration file and detect the definitions inside it.</div><div><br></div><div>#Configuration file:</div>
<div>[group1]</div><div>key1 = value1</div><div>key2 = value2<br clear="all"><div><br></div><div> Then I want to automatically load the group1. key1 and group2. key2, without knowing the name of group1 first.</div>
</div></div></blockquote><div><br></div></div></div><div>If you don’t know the group name, how would you know where to look in the parsed configuration for the resulting options?</div></div></div></blockquote><div><br></div>
<div style="">I can imagine something like this:</div><div style="">1. iterate over undefined groups in config;</div></div></div></div></blockquote><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div style="">2. select groups of interest (e.g. by prefix or some regular expression);</div><div style="">3. register options in them;</div>
<div style="">4. use those options.</div><div style=""><br></div><div style="">Registered group can be passed to a plugin/library that would register its options in it.</div></div></div></div></blockquote><div><br></div><div>If the options are related to the plugin, could the plugin just register them before it tries to use them?</div><div><br></div><div>I guess it’s not clear what problem you’re actually trying to solve by proposing this change to the way the config files are parsed. That doesn’t mean your idea is wrong, just that I can’t evaluate it or point out another solution. So what is it that you’re trying to do that has led to this suggestion?</div><div><br></div><div>Doug</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div style=""><br></div><div style="">So the only thing that oslo.config lacks in its interface here is some way to allow the first step. The rest can be overcomed with some sugar.</div>
</div><div><br></div>-- <br><br><div>Kind regards, Yuriy.</div>
</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>