[HOP-2268] Avoid state of metadata by not implementing IVariables

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.50
• Component/s: API
• Assignee: Unassigned
• Reporter: Matt Casters
• Created: 06/Dec/20 13:45
• Updated: 16/Dec/20 21:11
• Resolved: 11/Dec/20 21:48

Description

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.