tree d3521c9c1afb5fc318f6a01d74bb093c4b34cfb8
parent 4ffd34a8c528e2b3863af6f15ad78051007eddc6
author Brian Neradt <brian.neradt@gmail.com> 1602629303 -0500
committer GitHub <noreply@github.com> 1602629303 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfhi63CRBK7hj4Ov3rIwAAdHIIAIqNO0LUBAneWotcs4jxEHap
 dZqLufyzViTrMjtnI5uoafm0QjyowPWSPva2uBY8ziGeR+UyvVIc07V66pPEsT09
 Spgev98KpwdGl/8DWdHkkH0bcV9OsZ7eeHxkHLd19hNBRYKs+iIDvL7JSb+Uu+96
 LLzF6v28Iw3jCN2RrLMtsjBrky08DmmRH0v7OwtaUbRzd0uzIOPTpF5qdMoIkfKO
 8hVh/gnwbPVl/GF1f10107crMNgjuKpDVJF+MMtZMznXQobGr98/hLXh7wIwj0c9
 6+4KTWd+VEZUgAwyDzF+XuNjADuFBhPWub5UgrftHEYUUyqLdQYbdU+ui7A/36c=
 =BCQP
 -----END PGP SIGNATURE-----
 

Respecting default rolling_enabled in plugins. (#7275)

Some plugins indiscriminately enable log rolling without consideration
of the system value. This looks like it is just a mistake that went
unnoticed because we've always had this enabled. This patch changes a
couple plugins to respect the proxy.config.log.rolling_enabled value by
not overwriting it with TSTextLogObjectRollingEnabledSet unless
explicitly configured to do so.