[jira] [Commented] (ARIA-129) Undefined lifecycle operations are ignored without raising errors in install/uninstall

["Ran Ziv (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIA-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009732#comment-16009732 ] 

Ran Ziv commented on ARIA-129:
------------------------------

It's been decided that this is in fact the desired behavior - it can allow having a topology where there are separate node type hierarchies, where the built-in TOSCA workflows will only work on the TOSCA nodes but won't fail due to the existence of other types of nodes.

> Undefined lifecycle operations are ignored without raising errors in install/uninstall
> --------------------------------------------------------------------------------------
>
>                 Key: ARIA-129
>                 URL: https://issues.apache.org/jira/browse/ARIA-129
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Priority: Minor
>
> For a node which doesn't inherit from the root type and doesn't define the normative lifecycle operations, the built-in workflows (e.g. {{install}}) will simply skip the missing (or undefined) operations.
> It might be better to raise an error in such cases, stating that explicitness for skipping operations (e.g. by defining an empty operation, i.e. providing a null implementation) is required.



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