You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Laszlo Puskas (JIRA)" <ji...@apache.org> on 2017/03/23 13:37:41 UTC

[jira] [Commented] (AMBARI-20542) Fixed configuration type validation in case of blueprint deployments.

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

Laszlo Puskas commented on AMBARI-20542:
----------------------------------------

Corercted the config type validation logic.
Written unit test for it.
Patch attached.

> Fixed configuration type validation in case of blueprint deployments.
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-20542
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20542
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>         Attachments: AMBARI-20542.b-2.5.v1.patch
>
>
> Extended configuration type validation to the configurations posted in blueprints. (Previously only the configurations posted in the cluster template were considered) 
> Also a bug prohibits blueprint deployments that doesn't contain all the config types for services lisyted in the blueprint.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)