rdopiera at redhat.com
Fri Jun 26 08:21:17 UTC 2020
On Fri, Jun 26, 2020 at 9:28 AM Thomas Goirand <zigo at debian.org> wrote:
> On 6/25/20 2:00 AM, Adrian Turjak wrote:
> > On 24/06/20 8:34 pm, Thomas Goirand wrote:
> >> On 6/24/20 4:40 AM, Adrian Turjak wrote:
> >>> But of all the things to change, the config layer is the least of our
> >>> problems in Horizon, and with a good erb template (or jinja with
> >>> ansible) I have never had much pain with it.
> >> The biggest issue with a .erb template, is that it quickly gets
> >> outdated, and needs care for each new version of Horizon. I felt that
> >> pain multiple times recently.
> > But that happens for every service adding new config really.
> No. Other services using .ini have a default option embedded it the code
> itself (ie: that's how oslo.config works...), so if the option isn't
> there in the config file, it continues to work. This isn't the case with
Wait, what? Are you sure we are talking about the same Horizon?
It has defaults exactly the same way, and it literally works with an
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss