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

Posted to issues@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/07/12 09:02:00 UTC

[jira] [Updated] (ARIA-320) Extend plugin specification version constraints capabilities

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

Ran Ziv updated ARIA-320:
-------------------------
    Labels: orchestration plugins simple  (was: orchestration plugins)

> Extend plugin specification version constraints capabilities
> ------------------------------------------------------------
>
>                 Key: ARIA-320
>                 URL: https://issues.apache.org/jira/browse/ARIA-320
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Priority: Minor
>              Labels: orchestration, plugins, simple
>
> The plugin specification in the policies section currently supports specifying a single version; The plugin matching mechanism will choose any version equal or above that specified one, preferring the newest available.
> There should at least be a way to specify a specific version without having the plugin matching mechanism pick a newer one for you.
> There should probably also be more constraint capabilities, e.g. specifying a version range, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)