[
https://issues.apache.org/jira/browse/TS-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567578#comment-14567578
]
ASF GitHub Bot commented on TS-3650:
------------------------------------
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/206#issuecomment-107638211
The chat concensus seemed to be to change this to NULL, DEFAULT, EXPLICIT,
ENV. I'll change "SRC" to "SOURCE" as well - I was tempted to have "RECS" which
would be more consistent with the other REC values but that seemed even worse
scanning.
> Configuration variables should track their source
> -------------------------------------------------
>
> Key: TS-3650
> URL: https://issues.apache.org/jira/browse/TS-3650
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
>
> A configuration variable can get its value from a variety of sources. It
> would be useful to be able to programmatically determine that source. At a
> minimum the ability to determine if a variable was set explicitly in a
> configuration file vs. using a built in default value would be very useful.
> In addition this information should be made available to the administrator
> via {{traffic_ctl}} to aid in debugging.
> The proposed values are
> * {{DEFAULT}} - built in default, hard wired.
> * {{FILE}} - read from a configuration file.
> * {{API}} - set via an API of some sort ({{traffic_line}} etc.)
> * {{CLUSTER}} - set via cluster configuration
> * {{ENV}} - set from an environment variable
> In addition the value {{INVALID}} will be defined to use for the internal
> API, primarily as a value to return if the requested variable doesn't exist
> (in which case none of the previous values are reasonable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
