Github user dneuman64 commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/176
Thanks for the contribution @weifensh. While I agree there is an issue
with the approach we have taken to ensure everything is configured correctly,
which you outlined in TC-44, I don't think simply removing this code is the
best solution. We want to have the ability to reject the CrConfig if HTTPS
delivery services are configured without SSL certificates since it really is an
invalid configuration. The spirit of this code was to continuously log that
certificates were missing as to alert someone that action needs to be taken. I
am open to a different solution that solves the issue with the file leak while
still ensuring Traffic Router has a valid configuration, but I don't feel
inclined to accept this PR as is. Thoughts?
---
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.
---
