You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/05/01 09:04:04 UTC

[jira] [Created] (ARIA-170) Separate Workflow and Operation models

Ran Ziv created ARIA-170:
----------------------------

             Summary: Separate Workflow and Operation models
                 Key: ARIA-170
                 URL: https://issues.apache.org/jira/browse/ARIA-170
             Project: AriaTosca
          Issue Type: Task
            Reporter: Ran Ziv
            Priority: Minor


Workflow objects are currently modeled as Operations in storage. While they do have a lot in common, they're also different and should be separated into two different models.

If for some reason we'd prefer to keep them modeled as one, there should probably at least be a field stating whether a given object is a workflow or not, since right now the preferred method for figuring it out is a hackishly test for whether the {{interface}} field is set to {{None}}.




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