OK, you are referring to the "version" data type, and it is fully supported in ARIA, which includes:
1. Strict adherence to the (rather odd) specification and its regex 2. Proper support for TOSCA comparative constraints for versions (greater_than, lesser_than, etc.) 3. Comparisons also work properly in Python when comparing version instances On Mon, Aug 7, 2017 at 12:22 AM, D Jayachandran <[email protected] > wrote: > Hi Tal, > > I was referring to the section 3.2.2 in TOSCA 1.0. It seems the version > is part of both TOSCA 1.0 and TOSCA 1.1 > > http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile- > YAML/v1.0/os/TOSCA-Simple-Profile-YAML-v1.0-os.pdf > > Regards, > DJ > -----Original Message----- > From: Tal Liron [mailto:[email protected]] > Sent: Friday, August 04, 2017 9:39 PM > To: [email protected] > Subject: Re: Version support for different TOSCA types > > I think you are referring to TOSCA 1.1, which is on the roadmap but not > supported yet. > > You can of course create your own "version" property or attribute for node > types in TOSCA 1.0. > > On Fri, Aug 4, 2017 at 7:05 AM, D Jayachandran < > [email protected]> > wrote: > > > Hi, > > > > The TOSCA spec mentions about the version as a keyname for different > > type definitions(Node, Group, Interface, Artifacts, Data .. .) As > > mentioned in spec this is for the re-use of different types . Does > > ARIA support the version at this stage ? What is the scope of > > orchestrator when it comes to the version support ? > > > > > > > > Regards, > > DJ > > >
