+1
On Fri, May 10, 2019 at 11:13 AM Mark Moseley <moseleym...@gmail.com> wrote: > > As someone who deliberately breaks ATS's ability to modify configs, +1 :) > > On Fri, May 10, 2019 at 9:54 AM Leif Hedstrom <zw...@apache.org> wrote: >> >> >> >> On May 10, 2019, at 10:10 AM, Sudheer Vinukonda <sudheervinuko...@yahoo.com> >> wrote: >> >> Just to confirm, when you say "..make this behavior the only supported >> behavior in v9.0.0..", are you implying to not persist dynamic config >> changes into records.config? >> >> Assuming the answer is yes, I'm +1 on the proposal to make that as the >> de-facto and only behavior. >> >> >> Correct. ATS would no longer have the capabilities of writing configurations >> back to disk. >> >> — leif >> >> >> Thanks, >> >> Sudheer >> >> On Friday, May 10, 2019, 8:08:08 AM PDT, Leif Hedstrom <zw...@apache.org> >> wrote: >> >> >> Hi all, >> >> I’d like to propose that we remove the configuration option >> proxy.config.disable_configuration_modification, and make this behavior the >> only supported behavior in v9.0.0. I know of at least one user who would >> appreciate this … >> >> Doing so, would also let us eliminate all the Rollback.cc code, and the use >> of that. There’s no longer a point in rolling back old versions, since there >> won’t be any. >> >> And discuss. >> >> — Leif >> >>
