[ https://issues.apache.org/jira/browse/ARIA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ran Ziv updated ARIA-42: ------------------------ Issue Type: Story (was: Sub-task) Parent: (was: ARIA-40) > 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: Dan Kilman > > 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.4#6332)