[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741358#comment-14741358 ] 

Hadoop QA commented on AMBARI-13069:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12755421/AMBARI-13069.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3771//console

This message is automatically generated.

> Attributes of configuration property should be stack API driven
> ---------------------------------------------------------------
>
>                 Key: AMBARI-13069
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13069
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server, ambari-web, stacks
>    Affects Versions: 2.2.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13069.patch
>
>
> *Following attributes of configuration properties should be made stack API driven:*
> # Visibility of configuration property
> # display name of configuration property
> # Empty value validity of configuration property
> # Restriction of being configured only once on installation
> # overridable in config host group
> # Name of the property should be hidden
> *Achieving this task will be useful in following scenarios:*
> # custom services could be added with less changes in ambari-web code
> # Any issues related to configuration property attributes encountered on a deployed cluster can be addressed by making stack changes rather than redeploying ambari-web code with a fix. For example if a property tagged as not overridable if later desired to be made overridable on a deployed cluster will now require changing a boolean flag in stack configuration property rather than changing ambari-web code. 
> # Config property only in a specific stack can be attributed without writing stack specific logic in ambari-web



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)