[
https://issues.apache.org/jira/browse/ARIA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937044#comment-15937044
]
ASF GitHub Bot commented on ARIA-83:
------------------------------------
GitHub user tliron opened a pull request:
https://github.com/apache/incubator-ariatosca/pull/81
ARIA-83 Support ARIA profile for TOSCA
Notes:
* The TOSCA parser extension now supports "special" imports, in this case
the name is `aria-1.0`. This allows service template writers to just use the
name without having to know where it's located.
* Clarified, documented, and cleaned up models and other code having to
plugin specifications and workflows.
* Fixed all relevant tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-ariatosca
ARIA-83-aria-tosca-profile
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-ariatosca/pull/81.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #81
----
commit 34b353239eab457b089d575f39abe9b494653447
Author: Tal Liron <[email protected]>
Date: 2017-03-22T20:07:57Z
ARIA-83 Support ARIA profile for TOSCA
----
> Store built-in YAMLs in TOSCA extension
> ---------------------------------------
>
> Key: ARIA-83
> URL: https://issues.apache.org/jira/browse/ARIA-83
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Assignee: Tal Liron
>
> The built-in YAMLs (plugin/workflow policy definitions, built-in workflow
> policies, execution plugin's types and policy) should sit under the TOSCA
> extension to be easily importable.
> (This also includes first writing the execution plugin's types and policy)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
