Hello guys, following this I put a draft pr with a change to cover what it was discussed here.
https://github.com/apache/trafficserver/pull/9264 Please note there will be some record names that need to be changed, I have added a description about this change in the PR iself. The PR looks big but the majority of the code is not the core of the change, please if you have some time get a coffee(or your favourite beverage) and have a look. Best regards, Damian On Thu, Sep 22, 2022 at 6:52 PM Leif Hedstrom <zw...@apache.org> wrote: > > > On Sep 22, 2022, at 9:49 AM, Sudheer Vinukonda via users < > us...@trafficserver.apache.org> 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. > > > Agreed. A simple Perl script (or whatever) that reads a records.config and > converts it into records.yaml would be sufficient. > > I think in addition to the above, plugins such as conf_remap also needs to > support reading the same YAML format. Maybe we need to expose this as an > API to the plugin to avoid massive code duplications? > > — Leif > > > 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 > <https://urldefense.com/v3/__https://github.com/apache/trafficserver/pull/8212__;!!Op6eflyXZCqGR5I!FghAe84nZ4uu9leGQ-heOj3E5smATMD4D9DsuxkpeFH_DhUttDWlz9i2Hxz1CPuyPuALR2-wI_wb3WFxUpko$>> > and for a > quick look at how the records.yaml would look like, check here > <https://gist.github.com/brbzull0/e286e64e74f71061a6664cc961da6e51 > <https://urldefense.com/v3/__https://gist.github.com/brbzull0/e286e64e74f71061a6664cc961da6e51__;!!Op6eflyXZCqGR5I!FghAe84nZ4uu9leGQ-heOj3E5smATMD4D9DsuxkpeFH_DhUttDWlz9i2Hxz1CPuyPuALR2-wI_wb3SRvji1-$> > >. > > > Any feedback will be appreciated. > > Thanks, > Damian. > Yahoo > > >
