[jira] [Updated] (TS-4458) Disabling configuration modification breaks reloading
[ https://issues.apache.org/jira/browse/TS-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-4458: --- Summary: Disabling configuration modification breaks reloading (was: disabling configuration modification breaks reloading) > Disabling configuration modification breaks reloading > - > > Key: TS-4458 > URL: https://issues.apache.org/jira/browse/TS-4458 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: James Peach >Assignee: James Peach > Fix For: 7.0.0 > > > If you set {{proxy.config.disable_configuration_modification}} to 1, records > configuration callbacks are never registered, so if you update > {{records.config}} and then reload with {{traffic_ctl config reload}}, the > new configuration is not actually applied. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4458) disabling configuration modification breaks reloading
[ https://issues.apache.org/jira/browse/TS-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4458: -- Fix Version/s: 7.0.0 > disabling configuration modification breaks reloading > - > > Key: TS-4458 > URL: https://issues.apache.org/jira/browse/TS-4458 > Project: Traffic Server > Issue Type: Bug > Components: Configuration >Reporter: James Peach >Assignee: James Peach > Fix For: 7.0.0 > > > If you set {{proxy.config.disable_configuration_modification}} to 1, records > configuration callbacks are never registered, so if you update > {{records.config}} and then reload with {{traffic_ctl config reload}}, the > new configuration is not actually applied. -- This message was sent by Atlassian JIRA (v6.3.4#6332)