You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/05/19 19:16:39 UTC

[jira] [Closed] (TS-2218) create a standard way of getting the plugin configuration directory

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

Bryan Call closed TS-2218.
--------------------------

    Resolution: Won't Fix

I agree we should just use TSConfigDirGet().

> create a standard way of getting the plugin configuration directory
> -------------------------------------------------------------------
>
>                 Key: TS-2218
>                 URL: https://issues.apache.org/jira/browse/TS-2218
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Configuration, Plugins
>            Reporter: Bryan Call
>            Assignee: Bryan Call
>              Labels: api-change
>
> Currently some plugins use TSPluginDirGet() (/usr/local/libexec/trafficserver) and some have hard coded paths for getting the directory where the config files are set.
> I propose using sysconfdir/trafficserver/plugins/ (sysconfdir is defined in config.layout and is /usr/local/etc by default) as the default base directory for the plugin configuration.  Under this directory people will have their config file or a sub directory if there are a lot of config files for a plugin (e.g. sysconfdir/trafficserver/plugins/regex_remap/)
> There will be an API to get the plugin config directory called TSPluginConfigDir() and this will by default pass back sysconfdir/trafficserver/plugins/.  All plugins will use this API to get the configuration directory.
> There will also be a records.config option to override the default plugin config directory.  This option will be called proxy.config.plugin.plugin_config_dir.  This option will be set to NULL by default and the API will assume sysconfdir/trafficsever/plugins by default.



--
This message was sent by Atlassian JIRA
(v6.2#6252)