[jira] [Commented] (ARIA-42) Implement full blown mechanism for serializing an operation context

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARIA-42:
-----------------------------------------------------

Commit 59c266dc2bfe264c5ff6868b0fc8be8ef16f9d09 in incubator-ariatosca's branch refs/heads/ARIA-42-Generic-ctx-serialization-mechanism from mxmrlv
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=59c266d ]

ARIA-42-Generic-ctx-serialization-mechanism


> Implement full blown mechanism for serializing an operation context
> -------------------------------------------------------------------
>
>                 Key: ARIA-42
>                 URL: https://issues.apache.org/jira/browse/ARIA-42
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Dan Kilman
>            Assignee: Maxim Orlov
>
> The current mechanism at aria/orchestration/workflows/context/serialization.py is very limited.
> It serializes/deserializes the context.model and context.resource with hard coded knowledge of the actual implementation involved and even how they were initialized. Specifically:
> The model storage initialized is always expected to be sqlachemy based with no additional engine configuration (i.e. only the engine url is used to re-construct the sqlalchemy engine), similar logic applies to the instantiated sqlalchemy session.
> The resource storage initialized is always the file based resource storage.



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