[
https://issues.apache.org/jira/browse/AMBARI-23284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23284:
-----------------------------------
Description:
Add Ambari configuration data to stack/service advisor input data. Currently
the {{ldap-configuration}} data is passed in to the stack/service advisor.
However, generically all Ambari configuration data should be passed in.
For example, the current data set (in service.json) contains
{code:java}
{
... "services" : [],
... "configurations" : \{ ... }, "ambari-server-properties" : \{ ... },
... "ldap-configurations" : \{ ... }
}
{code}
"\{{ldap-configurations}}" may or may not exist depending on if LDAP
authentication/sync was setup. This should be treated generically and part of a
larger block of data named "\{{ambari-server-configuration}}". For example:
{code:java}
{
...
"services" : [],
...
"configurations" :
{ ... },
"ambari-server-properties" : { ... }
,
...
"ambari-server-configuration" : {
"ldap-configurations" :
{ ... }
,
...
}
}
{code}
was:
Add Ambari configuration data to stack/service advisor input data. Currently
the {{ldap-configuration}} data is passed in to the stack/service advisor.
However, generically all Ambari configuration data should be passed in.
For example, the current data set (in service.json) contains
{code}
{
... "services" : [],
... "configurations" : \{ ... }, "ambari-server-properties" : \{ ... },
... "ldap-configurations" : \{ ... }
}
"{{ldap-configurations}}" may or may not exist depending on if LDAP
authentication/sync was setup. This should be treated generically and part of a
larger block of data named "{{ambari-server-configuration}}". For example:
{code}
{
...
"services" : [],
...
"configurations" :
{ ... },
"ambari-server-properties" : { ... }
,
...
"ambari-server-configuration" : {
"ldap-configurations" :
{ ... }
,
...
}
}{code}
> Add Ambari configuration data to stack/service advisor input data
> -----------------------------------------------------------------
>
> Key: AMBARI-23284
> URL: https://issues.apache.org/jira/browse/AMBARI-23284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Fix For: 2.7.0
>
>
> Add Ambari configuration data to stack/service advisor input data. Currently
> the {{ldap-configuration}} data is passed in to the stack/service advisor.
> However, generically all Ambari configuration data should be passed in.
> For example, the current data set (in service.json) contains
> {code:java}
> {
> ... "services" : [],
> ... "configurations" : \{ ... }, "ambari-server-properties" : \{ ... },
> ... "ldap-configurations" : \{ ... }
> }
>
> {code}
>
> "\{{ldap-configurations}}" may or may not exist depending on if LDAP
> authentication/sync was setup. This should be treated generically and part of
> a larger block of data named "\{{ambari-server-configuration}}". For example:
> {code:java}
> {
> ...
> "services" : [],
> ...
> "configurations" :
> { ... },
> "ambari-server-properties" : { ... }
> ,
> ...
> "ambari-server-configuration" : {
> "ldap-configurations" :
> { ... }
> ,
> ...
> }
> }
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
