Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/301#issuecomment-151318976
I don't think it is that complex. All the machinery for doing this exists,
it just needs to be tied together in a sightly different way. My view is that
this approach adds complexity in the wrong place (though I definitely agree
that the config file management code can be refactored and simplified). One
approach would be to make an upcall to ```traffic_manager``` that installs a
"temporary watch" (ie. watch the file until the next reconfigure event).
Note that both ```ssl_multicert.config``` and ```remap.config``` have this
issue, so a general mechanism can be used to deal with both cases. Your
proposed solution also fails to update
```proxy.node.config.reconfigure_required``` correctly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
