Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
Date: Fri, 19 May 2017 11:15:04 +0000 (UTC)
From: "Ran Ziv (JIRA)" <jira@apache.org>
To: issues@ariatosca.apache.org
Message-ID: <JIRA.13024794.1480603807000.249426.1495192504790@Atlassian.JIRA>
In-Reply-To: <JIRA.13024794.1480603807000@Atlassian.JIRA>
References: <JIRA.13024794.1480603807000@Atlassian.JIRA> <JIRA.13024794.1480603807580@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (ARIA-37) Generify ARIA's built-in workflows
 interface names
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 19 May 2017 11:15:10 -0000


     [ https://issues.apache.org/jira/browse/ARIA-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ran Ziv resolved ARIA-37.
-------------------------
    Resolution: Won't Fix
      Assignee: Ran Ziv

It's been decided that the built-in workflows currently in ARIA are TOSCA-specific and as such they're not meant to be extended with custom interface names.

Instead, custom workflows may be written, including generic ones which would allow what this issue topic mentions - but those will be separate from the built-in workflows.

> Generify ARIA's built-in workflows interface names
> --------------------------------------------------
>
>                 Key: ARIA-37
>                 URL: https://issues.apache.org/jira/browse/ARIA-37
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Assignee: Ran Ziv
>
> Generify ARIA's built-in workflows interface names, so that they can be injected by external components utilizing ARIA


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)