You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2014/08/28 21:39:09 UTC

[jira] [Resolved] (SLIDER-346) Application metainfo should be able to explicitly specify available config files

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

Sumit Mohanty resolved SLIDER-346.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Slider 0.60

> Application metainfo should be able to explicitly specify available config files
> --------------------------------------------------------------------------------
>
>                 Key: SLIDER-346
>                 URL: https://issues.apache.org/jira/browse/SLIDER-346
>             Project: Slider
>          Issue Type: Bug
>          Components: app-package
>    Affects Versions: Slider 0.50
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: Slider 0.60
>
>
> When an application package is created, the config files required by the application is implicitly handled by the package scripts. Slider should modify the metainfo schema to explicitly contain the details of the config files expected by the application.
> Proposed structure can be:
> {noformat}
> <configFile>
>   <type>env</type>
>   <fileName>hbase-policy.xml</fileName>
>   <dictionaryName>hbase-policy</dictionaryName>
> </configFile>
> {noformat}
> where:
> * type - format of the file when deployed on disk - can also be used by registry to allow formatted file downloads
> * name - name of the file when deployed on the disk
> * dictionaryName - name tag of the config properties that influence the content of the file



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