[jira] [Updated] (TS-4463) Explicit reconfiguration should not check for file changes

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-4463:
------------------------------
    Fix Version/s:     (was: 7.0.0)
                   8.0.0

> Explicit reconfiguration should not check for file changes
> ----------------------------------------------------------
>
>                 Key: TS-4463
>                 URL: https://issues.apache.org/jira/browse/TS-4463
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Management API
>            Reporter: James Peach
>            Assignee: James Peach
>              Labels: incompatible
>             Fix For: 8.0.0
>
>
> When an operator runs {{traffic_ctl config reload}} that is an explicit signal that they want the configuration reloaded. We should not second guess that by checking whether files are updated like we do today.
> One use case for this is when {{proxy.config.disable_configuration_modification}} is enabled and you change configuration in memory with the API. It is surprising and confusing to have to touch {{records.config}} to restore the old values.
> Consider whether we should add a {{\-\-changed-only}} flag to only reload changed configuration. I'm leaning against that but could be persuaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)