Open Stack

Excerpts from Jesse Pretorius's message of 2017-09-28 17:17:55 +0000:
> On 9/28/17, 5:11 PM, "Doug Hellmann" <doug at doughellmann.com> wrote:
> 
> > In the past we had trouble checking those files into git and gating
> > against the results being "up to date" or not changing in any way
> > because configuration options that end up in the file are defined in
> > libraries used by the services. So as long as the implementation you're
> > considering does not check configuration files into git, but generates
> > them and then inserts them into the package, it should be fine.
> 
> I’m guessing that the aut-generated files you’re referring to are the .conf files? For the most part, those are being left out of my proposed patches unless the project team specifically requests their inclusion. My patches are focused on the far more static files - policy.json if it exists (yes, the policy-in-code will remove those in time), api-paste, rootwrap.conf and the rootwrap.d contents. As far as I know none of these are auto-generated. If they are, I’m all ears to learn how!
> 

Ah, yes, I was talking about oslo.config files but those other files
are more static and shouldn't present the same issue.

Doug