[
https://issues.apache.org/jira/browse/AMBARI-11964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Vasilenko updated AMBARI-11964:
--------------------------------------
Description:
Currently the logic to hide custom configuration sections is hardcoded in the
/ambari-web/app/models/stack_service.js
{noformat}
// Add custom section for every configType to all the services
configTypes.forEach(function (type) {
var configTypesWithNoCustomSection =
['capacity-scheduler','mapred-queue-acls','flume-conf',
'pig-properties','topology','users-ldif'];
if (type.endsWith('-env') || type.endsWith('-log4j') ||
configTypesWithNoCustomSection.contains(type)) {
return;
}
{noformat}
It will be beneficial to have a declarative way for the services to hide the
custom configuration section for the given configuration XML.
was:
Currently the logic to hide custom configuration sections is hardcoded in the
/ambari-web/app/models/stack_service.js
// Add custom section for every configType to all the services
configTypes.forEach(function (type) {
var configTypesWithNoCustomSection =
['capacity-scheduler','mapred-queue-acls','flume-conf',
'pig-properties','topology','users-ldif'];
if (type.endsWith('-env') || type.endsWith('-log4j') ||
configTypesWithNoCustomSection.contains(type)) {
return;
}
It will be beneficial to have a declarative way for the services to hide the
custom configuration section for the given configuration XML.
> Allow services to hide "custom" configurations
> ----------------------------------------------
>
> Key: AMBARI-11964
> URL: https://issues.apache.org/jira/browse/AMBARI-11964
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Dmitry Vasilenko
>
> Currently the logic to hide custom configuration sections is hardcoded in the
> /ambari-web/app/models/stack_service.js
> {noformat}
> // Add custom section for every configType to all the services
> configTypes.forEach(function (type) {
> var configTypesWithNoCustomSection =
> ['capacity-scheduler','mapred-queue-acls','flume-conf',
> 'pig-properties','topology','users-ldif'];
> if (type.endsWith('-env') || type.endsWith('-log4j') ||
> configTypesWithNoCustomSection.contains(type)) {
> return;
> }
> {noformat}
> It will be beneficial to have a declarative way for the services to hide the
> custom configuration section for the given configuration XML.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
