The Operator tooling today reads in a config file, parses it, then writes it to a common location on disk. This should instead be changed such that the config file is parsed in a single location and the config object is instead passed through the call stack.
This will enable support for #265.
The Operator tooling today reads in a config file, parses it, then writes it to a common location on disk. This should instead be changed such that the config file is parsed in a single location and the config object is instead passed through the call stack.
This will enable support for #265.