[
https://issues.apache.org/jira/browse/AMBARI-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shivani Gupta resolved AMBARI-6977.
-----------------------------------
Resolution: Duplicate
Duplicate of AMBARI-4671
> Support changing the name of an existing cluster via API
> --------------------------------------------------------
>
> Key: AMBARI-6977
> URL: https://issues.apache.org/jira/browse/AMBARI-6977
> Project: Ambari
> Issue Type: New Feature
> Affects Versions: 1.7.0
> Reporter: Shivani Gupta
> Fix For: 1.7.0
>
>
> 1) During cluster install (either via Blueprints or Wizard), user specifies
> the "cluster name".
> 2) This becomes the cluster name ID, used in the Ambari Web UI and in the API
> to uniquely identify the cluster.
> Provide ability to change the cluster name ID. By changing that cluster name
> ID, the API calls for that cluster will change too (for example, changing the
> name from ClusterX to Cluster Y means /api/v1/clusters/ClusterX will then
> become /api/v1/clusters/ClusterY).
> Expose this rename operation via Ambari API; this should not require direct
> SQL against the Ambari database
--
This message was sent by Atlassian JIRA
(v6.2#6252)
