You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2015/09/11 08:57:45 UTC
[jira] [Updated] (AMBARI-13069) Attributes of configuration
property should be stack API driven
[ 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
*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.
> 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: Bug
> Components: ambari-server, ambari-web, stacks
> Affects Versions: 2.2.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Fix For: 2.2.0
>
>
> *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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)