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/30 20:32:52 UTC

[jira] [Resolved] (SLIDER-125) Cleanup app config naming and structure

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

Sumit Mohanty resolved SLIDER-125.
----------------------------------

    Resolution: Not a Problem

With the ability to ingest default configs, the size of appConfig.json is much more manageable.

> Cleanup app config naming and structure
> ---------------------------------------
>
>                 Key: SLIDER-125
>                 URL: https://issues.apache.org/jira/browse/SLIDER-125
>             Project: Slider
>          Issue Type: Bug
>          Components: appspec
>    Affects Versions: Slider 0.40
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>
> Correctly, specifying application configuration (currently, received through --template) is critical for successful application creation. There exists a structure today through variable naming convention but it is not intuitive.
> * Some variables do not have any prefix
> * Variables can be organized into sections - e.g. "for Slider" or "for App"
> * "global" is not a great name for app variables that do not go into any config file 
> Modify the documentation to describe the structure and naming convention.



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