ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10647) Configs should be removed/added when /recommendations says so
Date Wed, 22 Apr 2015 10:19:58 GMT

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

Oleg Nechiporenko commented on AMBARI-10647:
--------------------------------------------

+1 for additional patch

> Configs should be removed/added when /recommendations says so
> -------------------------------------------------------------
>
>                 Key: AMBARI-10647
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10647
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10647.patch, AMBARI-10647_2.patch
>
>
> /recommendations endpoint can remove and add new configs via its response. 
> New configs will be just be provided as key/values in the recommendations - the UI should
add appropriate config to the UI and show the value. Saving should persist this key/value
on server.
> Removed configs will have a {{property_attributes}} called {{delete:true}}. If this flag
is present, the config should be removed from the UI and not persisted in the API.



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

Mime
View raw message