You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Swapan Shridhar (JIRA)" <ji...@apache.org> on 2017/11/10 23:58:00 UTC

[jira] [Resolved] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

     [ https://issues.apache.org/jira/browse/AMBARI-22366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapan Shridhar resolved AMBARI-22366.
--------------------------------------
    Resolution: Fixed

> POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-22366
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22366
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file *setting(s)* : *http://<host>:<port>/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://<host>:<port>/api/v1/clusters/[[clusterName]]/settings*, where 
>    -- the cluster settings would be initially read from the above mentioned read-only API : *http://<host>:<port>/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)