Open Stack

On Wed, Feb 17, 2016 at 2:29 PM Doug Hellmann <doug at doughellmann.com> wrote:

>
> That change only affects sample files and documentation. It has been
> possible for applications to override config defaults for ages. Were we
> blocked on making effective use of that because of the doc issue for a
> long time?


Sample files and documentation are where we want this. If we override the
defaults, and then a config file is modified to again overwrite those
defaults, then suddenly a magic internal value that is presumably required
for the feature to function properly disappears. What we're looking to do
is guide operators and deployers to knowing what should live in their
config file for the feature to work properly. Hence the change you created
being what we need.

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160218/cca8bfa1/attachment.html>