bryancall commented on issue #13011: URL: https://github.com/apache/trafficserver/issues/13011#issuecomment-4119932760
The main reason for moving to YAML was to adopt a standard configuration format and to support splitting configuration across multiple files or keeping everything in a single file — whatever works best for your deployment. As a practical stopgap for migrating: you don't have to rewrite your config management at all. Keep generating `records.config` the way you do today and just run [`convert2yaml.py`](https://github.com/apache/trafficserver/blob/master/tools/records/convert2yaml.py) as a post-processing step. Your existing tooling stays untouched. And when you're ready to update the tooling properly, the mapping between `records.config` and `records.yaml` is a straightforward one-to-one conversion — it's the kind of thing modern AI coding tools can knock out in an afternoon. I'm going to close this issue, but if you run into specific problems during a migration to 10, please open new issues and we'll help where we can. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
