[ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaimin D Jetly updated AMBARI-13069: ------------------------------------ Description: *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 # Unit of the property *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 was: *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 > 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, AMBARI-13069_2.patch, > AMBARI-13069_3.patch, AMBARI-13069_4.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 > # Unit of the property > *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)