[jira] [Resolved] (SLIDER-316) Add ability to accept a configuration files as is

["Sumit Mohanty (JIRA)" <ji...@apache.org>]

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

Sumit Mohanty resolved SLIDER-316.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Slider 0.60

> Add ability to accept a configuration files as is
> -------------------------------------------------
>
>                 Key: SLIDER-316
>                 URL: https://issues.apache.org/jira/browse/SLIDER-316
>             Project: Slider
>          Issue Type: Bug
>          Components: agent-provider, appmaster
>    Affects Versions: Slider 0.40
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: Slider 0.60
>
>
> An application package may not parameterize all the config file. In that case, Slider should have the ability to accept one or more config files in a folder that will be copied as is to the application config folder.
> Whether these config files over-ride the config file generated by the application package or not is the responsibility of the application package. The recommendation is to prioritize generate configuration files. 
> This means:
> * Application package must fully parameterized a specific config file such that the full file can be auto-generated
> * Application package can optionally accept other files to be dropped into the config folder
> * User provides configuration parameters (e.g. parameters for the site.xml)
> * User may provide a set of files in addition to above (e.g. log4j.properties)
> * WHen the application is instantiated
> ** default config folder is created when the tarball is expanded
> ** this folder is over-written by the supplied config files if any
> ** the generated config files are then dropped into the config folder



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