[
https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949193#comment-15949193
]
ASF subversion and git services commented on ARIA-133:
------------------------------------------------------
Commit 941d85c0ed622b6b233f38f853145c6a55120dec in incubator-ariatosca's branch
refs/heads/ARIA-86-Create-a-basic-Hello-World-blueprint-example from [~avia]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=941d85c ]
ARIA-133 Add status-related properties to the Execution, Task and Node models
We are adding these properties so it will be easier to filter those models
from storage according to their status, and to not make use of the their
`status` constants outside of the models themselves.
It should be noted, since we currently have the concept of `StubTasks`
(that are not part of the model), we had to implement the same logic for
them, although they don't direct access to the state constants of the
task model. We did this since they are treated as 'regular' model tasks
in some parts of the code.
> Add status-related properties to Execution, Task and Node models
> ----------------------------------------------------------------
>
> Key: ARIA-133
> URL: https://issues.apache.org/jira/browse/ARIA-133
> Project: AriaTosca
> Issue Type: Task
> Reporter: Avia Efrat
> Assignee: Avia Efrat
> Priority: Minor
> Fix For: 0.1.0
>
>
> We are adding those properties so it will be easier to filter these models
> from storage according to their status, and to not make use of the their
> `status` constants outside of the models themselves.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
