[
https://issues.apache.org/jira/browse/AMBARI-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161694#comment-14161694
]
Hudson commented on AMBARI-7669:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #495 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/495/])
AMBARI-7669 Missing version list control for "read-only" cluster user. (Ievgen
Fialkovskyi via atkach) (atkach:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bba0d5446c3af8394a82c72d844deaf88d77d661)
* ambari-web/app/templates/common/configs/config_history_flow.hbs
> Missing version list control for "read-only" cluster user
> ---------------------------------------------------------
>
> Key: AMBARI-7669
> URL: https://issues.apache.org/jira/browse/AMBARI-7669
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.7.0
>
> Attachments: AMBARI-7669.patch, missing-version-control.tiff
>
>
> For a cluster read-only user, when you login and look at Configs (for
> example, Services HDFS > Configs), you should still have the version control
> to drop-down the list of configs (on the service config bar on the left of
> the version badge). A read-only can just have a limited right-cascading menu
> option per version to "View" (i.e. no compare or make current...similar to
> the scv hover dialog only includes "View").
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
