Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9578B200C79 for ; Fri, 19 May 2017 11:53:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 93DA2160BD2; Fri, 19 May 2017 09:53:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DAF2F160BBE for ; Fri, 19 May 2017 11:53:07 +0200 (CEST) Received: (qmail 8413 invoked by uid 500); 19 May 2017 09:53:07 -0000 Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ariatosca.incubator.apache.org Delivered-To: mailing list issues@ariatosca.incubator.apache.org Received: (qmail 8401 invoked by uid 99); 19 May 2017 09:53:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 May 2017 09:53:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BC98B1A0E25 for ; Fri, 19 May 2017 09:53:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id pU5Qf7q2NQXO for ; Fri, 19 May 2017 09:53:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 379005FDB6 for ; Fri, 19 May 2017 09:53:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7EB5FE07E1 for ; Fri, 19 May 2017 09:53:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 326D521B58 for ; Fri, 19 May 2017 09:53:04 +0000 (UTC) Date: Fri, 19 May 2017 09:53:04 +0000 (UTC) From: "Ran Ziv (JIRA)" To: issues@ariatosca.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARIA-94) Validate operations exist before executing workflow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 19 May 2017 09:53:08 -0000 [ https://issues.apache.org/jira/browse/ARIA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv updated ARIA-94: ------------------------ Description: There should be a validation that all operations mapped in the template do indeed exist prior to workflow execution - it's probably best to simply do this when creating a service, right after validating the relevant plugins all exist. Note that this validation would have to run in a subprocess and use the plugin mechanism to load each plugin's environment. was: There should be a validation that all operations mapped in the template do indeed exist prior to workflow execution - it's probably best to simply do this when creating a deployment, right after validating the relevant plugins all exist. Note that this validation would have to run in a subprocess and use the plugin mechanism to load each plugin's environment. > Validate operations exist before executing workflow > --------------------------------------------------- > > Key: ARIA-94 > URL: https://issues.apache.org/jira/browse/ARIA-94 > Project: AriaTosca > Issue Type: Story > Reporter: Ran Ziv > Priority: Minor > > There should be a validation that all operations mapped in the template do indeed exist prior to workflow execution - it's probably best to simply do this when creating a service, right after validating the relevant plugins all exist. > Note that this validation would have to run in a subprocess and use the plugin mechanism to load each plugin's environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)