You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/08/22 15:56:13 UTC

[jira] [Resolved] (AMBARI-6959) Stacks service API: configTypes filed should return contained configuration files for the service

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

Andrew Onischuk resolved AMBARI-6959.
-------------------------------------

    Resolution: Fixed

Committed to trunk

> Stacks service API: configTypes filed should return contained configuration files for the service
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-6959
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6959
>             Project: Ambari
>          Issue Type: Task
>          Components: site
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Andrew Onischuk
>            Priority: Critical
>             Fix For: 1.7.0
>
>
> Right now service metainfo definition provides 
> configuration-dependencies tag that is exposed in the API as configTypes field.
> *configTypes:*
> Name of all the configuration types that the service carries in it's configuration folder. UI will use this to *display configType section and configurations on the service config page*.
> As of now UI Uses the configTypes files that actually gives configDependencies values by hard-coding the references to the services in the web-code which can lead to potential bugs when service metainfo.xml is changed with to address just one functionality



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