Single format is fine with me as long as start up will fail if there is no records.yaml and there is an old style records.config present. As I recall in the ipallow upgrade it would just go with defaults. That caused a number of us a day or so debugging.
On Thu, Sep 22, 2022, 10:50 AM Sudheer Vinukonda <sudheervinuko...@yahoo.com.invalid> wrote: > My vote is for #2 (ie support a single format), but, if possible, it'd be > great if we can automatically convert the existing config files into YAML > as part of the upgrade. At the very least, we should provide a tool + steps > on how to convert even if it's manual. > On Thursday, September 22, 2022 at 08:42:35 AM PDT, Damian Meden < > dme...@apache.org> wrote: > > Hello guys, as a part of the moving to yaml, I plan to work on converting > our records.config to records.yaml, this has been going on for a while now > so hopefully I can get some traction now. > As a *phase 1* of this task and aiming for 10 release, the plan is just to > keep the original librecord internals and just have a yaml parsing layer to > fill in the existing records similar to the current process but having the > records.yaml as input file. > Now after having some talks with some of you separately one think came up > in common: > > > 1. Do we want to have dual parsing, like we did with ip_allow.yaml or: > 2. Single yaml parsing and ask everyone to just convert to yaml for 10 > release. > > > More details about the records.yaml I put together some time ago can be > found here <https://github.com/apache/trafficserver/pull/8212> and for a > quick look at how the records.yaml would look like, check here > <https://gist.github.com/brbzull0/e286e64e74f71061a6664cc961da6e51>. > > > Any feedback will be appreciated. > > Thanks, > Damian. > Yahoo >
