Open Stack

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!



________________________________
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com and delete the original message. Your cooperation is appreciated.