Re: Version support for different TOSCA types

[Tal Liron]

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 
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
>

Version support for different TOSCA types

[D Jayachandran]

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

Digest for ASF's Slack

[Digest]

Here’s your digest for today! 
#ariatosca
undefined: [UPDATE] Finished reviewing the instantiation refactoring pr 
(ARIA-174). 

Created a document describing my current (and not final) constrains and 
concerns regarding service composition:

Later, as this document matures, I will share it with the our whole community 
for further discussion, and add it as a public resource.
undefined: [UPDATE] ugh, very dispiriting ... i was working for two days now 
trying to fix so many problems with aria-extensions-cloudify, but apparently i 
based my branch off the wrong branch, not master. :confused: so it was all for 
nothing. :(:(
 back to the drawing board ...
 meanwhile, i hope we can merge my PR on the ariatosca repo. can one of you 
verify?


#general


#random