[
https://issues.apache.org/jira/browse/TS-1882?focusedWorklogId=28286&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28286
]
ASF GitHub Bot logged work on TS-1882:
--------------------------------------
Author: ASF GitHub Bot
Created on: 07/Sep/16 16:08
Start Date: 07/Sep/16 16:08
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/971#discussion_r77854033
--- Diff: proxy/Main.cc ---
@@ -476,6 +476,18 @@ check_config_directories(void)
}
}
+namespace {
+ // Values with names that have this prefix are exempted from being
considered "unrecognized".
+ const char PLUGIN_CONFIG_RECORD_PREFIX[] = "proxy.config.plugin.";
--- End diff --
I think the right check is to test whether there are any unregistered local
or config records. This can be done periodically since new records can be added
at config reload time. A records that is present in ``records.config`` will be
not be marked as registered intul a plugin calls ``TSMgmtStringCreate()`` or
the equivalent.
Issue Time Tracking
-------------------
Worklog Id: (was: 28286)
Time Spent: 50m (was: 40m)
> ATS doesn't warn about unknown config items
> -------------------------------------------
>
> Key: TS-1882
> URL: https://issues.apache.org/jira/browse/TS-1882
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: Ebrahim Mohammadi
> Assignee: Alan M. Carroll
> Fix For: 7.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Apache Traffic Server doesn't warn about unknown configuration file items. It
> can cause huge confusions, specially in case of trying to get features of a
> newer version to work on an older installed version by mistake, as I found
> out the hard way!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
