16030aeec8
This commit reworks mechanism how context chain is built at each point. The goal was to make entire chain be dependent on format version number. This would allow for example to use yaql 1.0 legacy mode context for MuranoPL/1.0 and not to use it for 2.0. Not the entire chain is built on demand up to the root instead of attaching to existed parent context as it was before. DSL host (engine) is no more required to have custom MuranoDslExecutor implementation but a new ContextManager interface that is used to control contexts on each layer. Engine uses this interface to register system classes and engine level yaql functions. Also a ContextManager is a foundation for method mocking because now all MuranoPL methods are yaql functions stored in context and with ContextManager it is possible to inject/replace function in each scope ( global, package, class, object) Partially implements: blueprint murano-versioning Change-Id: I0a553e8044061fe780a83bc04d70b8f80580988f |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| api.py | ||
| cfapi.py | ||
| db_manage.py | ||
| engine.py | ||
| manage.py | ||
| test_runner.py | ||