[
https://issues.apache.org/jira/browse/AMBARI-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107353#comment-14107353
]
Hudson commented on AMBARI-6959:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2/])
Revert "AMBARI-6959. Stacks service API: configTypes filed should return
contained configuration files for the service (aonishuk)" (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a1ab301185f40a9f3d01a062c9c1df4251e427e5)
*
ambari-server/src/test/java/org/apache/ambari/server/api/util/StackExtensionHelperTest.java
*
ambari-server/src/main/resources/stacks/HDP/1.3.2/services/MAPREDUCE/configuration/core-site.xml
*
ambari-server/src/main/java/org/apache/ambari/server/api/util/StackExtensionHelper.java
*
ambari-server/src/main/resources/stacks/HDP/2.1/services/YARN/configuration/core-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/configuration/core-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/configuration-mapred/core-site.xml
> 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)
