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

Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2015/01/19 15:58:34 UTC

[jira] [Updated] (AMBARI-9133) Views: min and max version

     [ https://issues.apache.org/jira/browse/AMBARI-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Beerbower updated AMBARI-9133:
----------------------------------
    Attachment: AMBARI-9133.patch

> Views: min and max version
> --------------------------
>
>                 Key: AMBARI-9133
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9133
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9133.patch
>
>
> Add support for including optional min, max or min+max Ambari version in view.xml. This can include exact versions or variables. A few examples:
> <minVersion>1.7.0</minVersion>
> <minVersion>1.7.*</minVersion>
> <maxVersion>1.*</maxVersion>
> On deploy, ambari should validate the view meets the min/max specified and if not, not deploy and produce an error in the log with the details (for example: "view requires minimum ambari version 1.7") 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)