+ 1
-Bryan
> On Mar 14, 2019, at 11:26 AM, Leif Hedstrom wrote:
>
> Hi all,
>
> As we’re making more progress migrating towards YAML configurations, I’d like
> to make two proposals for v9.0.0:
>
>
> 1) As we migrate a configuration to the new YAML format, we only support
> YAML. I.e. no
> On Mar 14, 2019, at 5:07 PM, Masaori Koshiba wrote:
>
> proxy.config.ssl.server.multicert.filename
Yes, it should also be removed.
— leif
>
> 2) We remove the following configurations from records.config, and only
> support the default config files names (e.g. ip_allow.yaml).
> proxy.config.cache.storage_filename
> proxy.config.cache.control.filename
> proxy.config.cache.ip_allow.filename
> proxy.confi
> On Mar 14, 2019, at 1:29 PM, John Rushford wrote:
>
> Leif,
>
> Your proposal seems fine to me. I have a PR on github that converts the
> existing parent.config to YAML,
> https://github.com/apache/trafficserver/pull/4857
> In this PR, I had made it backwards compatible with the existing f
Leif,
Your proposal seems fine to me. I have a PR on github that converts the
existing parent.config to YAML,
https://github.com/apache/trafficserver/pull/4857
In this PR, I had made it backwards compatible with the existing format.
The change involves a lot of changes to the ControlMatcher which
Hi all,
As we’re making more progress migrating towards YAML configurations, I’d like
to make two proposals for v9.0.0:
1) As we migrate a configuration to the new YAML format, we only support YAML.
I.e. no backwards compatibility layers. Of course, we only break such
compatibility in major
