You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/09/12 22:38:20 UTC
[jira] [Updated] (AMBARI-18332) Blueprints: API should make
available "setting" property from blueprint
[ https://issues.apache.org/jira/browse/AMBARI-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nahappan Somasundaram updated AMBARI-18332:
-------------------------------------------
Description:
The following APIs do not retrieve *setting* section from the blueprint that was used during deployment:
{code}
http://<hostname>:<port>/api/v1/blueprints/<blueprint_name>
{code}
was:
The following APIs do not retrieve *setting* section from the blueprint that was used during deployment:
{code}
http://<hostname>:<port>/api/v1/blueprints/<blueprint_name>
http://<hostname>:<port>/api/v1/clusters/<cluster_name>?format=blueprint
{code}
> Blueprints: API should make available "setting" property from blueprint
> -----------------------------------------------------------------------
>
> Key: AMBARI-18332
> URL: https://issues.apache.org/jira/browse/AMBARI-18332
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
>
> The following APIs do not retrieve *setting* section from the blueprint that was used during deployment:
> {code}
> http://<hostname>:<port>/api/v1/blueprints/<blueprint_name>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)