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/04/03 12:49:41 UTC

[jira] [Updated] (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:all-tabpanel ]

Laszlo Puskas updated AMBARI-20542:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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
>            Priority: Blocker
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20542.b-2.5.v2.patch, AMBARI-20542.trunk.v2.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 listed in the blueprint.



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