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/09/13 11:26:00 UTC

[jira] [Created] (ARIA-369) Plugin upgrade for existing services

Ran Ziv created ARIA-369:
----------------------------

             Summary: Plugin upgrade for existing services
                 Key: ARIA-369
                 URL: https://issues.apache.org/jira/browse/ARIA-369
             Project: AriaTosca
          Issue Type: Story
            Reporter: Ran Ziv
            Priority: Trivial


Plugin specifications declared in service-templates are matched against an actual plugin implementation at service creation time.

This means that if a service-template declares usage of plugin X (without any version restrictions), and at service creation time plugin X is installed in version 1.0, it will be used for the entirety of the service's life - even if at some point in the future, a newer version of plugin X is installed.

It may be better to have this as a configurable option (perhaps on a per-service basis?) - On the one hand, it will allow easy access for bug fixes and possibly new features to be used from plugins. On the other hand, it may cause confusion, as different executions that were made on a given service may have used different versions of the same plugin.



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