[
https://issues.apache.org/jira/browse/ARIA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858257#comment-15858257
]
ASF GitHub Bot commented on ARIA-42:
------------------------------------
Github user ran-z commented on a diff in the pull request:
https://github.com/apache/incubator-ariatosca/pull/68#discussion_r100119147
--- Diff: aria/storage/core.py ---
@@ -66,10 +67,10 @@ def __init__(self,
self.registered = {}
self._initiator = initiator
self._initiator_kwargs = initiator_kwargs or {}
+ self._api_kwargs = api_kwargs or {}
+ self._additional_api_kwargs = {}
--- End diff --
unpicklable
> 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)
