Hi Tal, Thanks for the information on the plugin version, and this approach seems to be fine with the version being an optional one.
I was under the assumption version is a mandatory thing and having this validation at the service creation would have the user recreate the service model when a newer version of plugin is installed. Regards, DJ -----Original Message----- From: Tal Liron [mailto:t...@gigaspaces.com] Sent: Tuesday, July 11, 2017 4:52 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Plugin validation That's a good question. :) Actually, in the service template you do not pin down the plugin, but rather specify the plugin and a minimum version that you need. During instantiation there might be a higher version of the plugin that would be matched. Once instantiated the plugin version is "locked" for that service instance. If you then install a newer version of the plugin, and create a new service instance, the second service instance would use the higher version. All this is done to make sure that the service remains stable. It would of course be possible to verify this earlier, but it seemed unnecessary. What advantage do you see in verifying the existing of the plugin during the service template parsing stage? On Tue, Jul 11, 2017 at 12:04 PM, D Jayachandran < d.jayachand...@ericsson.com> wrote: > Hi, > > With current implementation, the plugin validation in a service > template happens during the service creation (instantiation of service model). > Will it be appropriate if we have this plugin validation happening > during the service-template creation itself ? > > > > Regards, > DJ >
