ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18332) Blueprints: API should make available "setting" property from blueprint
Date Thu, 15 Sep 2016 00:40:20 GMT

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

Hudson commented on AMBARI-18332:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/])
AMBARI-18332: Blueprints: API should make available "setting" property (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b89d6866e369906902f759a7a5d2ba865e8cbe0])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintResourceProvider.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintResourceProviderTest.java


> 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
>
>         Attachments: rb51851.patch
>
>
> 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)

Mime
View raw message