Metadata objects are now implementing IVariables.
While this makes it easy for objects like PipelineMeta and DatabaseMeta to resolve variables at runtime it causes 2 main issues:
- the metadata now has a state associated with the run-time forcing cloning, copying, re-loading of the metadata for each execution
- More importantly, it's often unclear where the variables came from, how they were set, if they were set at all and if all sources for variables were taken into account.
|Update kettle to hop plugin porting documentation||Resolved||Unassigned|