[
https://issues.apache.org/jira/browse/AMBARI-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-13280:
------------------------------------
Summary: Enhanced Configs work to add Ranger User Info tab (was: Enhanced
Configs ui work to add Ranger User Info tab)
> Enhanced Configs work to add Ranger User Info tab
> -------------------------------------------------
>
> Key: AMBARI-13280
> URL: https://issues.apache.org/jira/browse/AMBARI-13280
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
> Affects Versions: 2.1.3
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13280.patch
>
>
> Currently, there is a notion of tab, section and subsection in UI which is
> completely theme driven from stack API endpoint.
> subsection is the last container that contains set of configs. This is
> achieved by registering each config with a subsection in service theme.
> As part of this ticket add a notion of subsection-tabs (a group of tabs)
> which can be optionally present inside a subsection. Any config can register
> only to a subsection as it does currently or can register to a subsection and
> to an individual tab of a subsection-tab located inside the subsection.
> For now, Layout of a subsection-tabs (a group of tabs) in a subsection is
> always at last. This means that if there are configs that are not mapped to
> any individual tab of subsection-tabs then they will be placed before
> subsection-tabs. Orientation of configs inside subsection-tabs should be in
> order of their occurrence in theme.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
