Thanks for the replies so far from all. It does seem like it is both a
problem with the fact that I decided to explicitly version our
application modules and provide a mechanism for tieing configuration
"blueprints" in the ENC side to the version of the application module
in use, but no such mechan
> Whenever we want to add additional parameters to certain classes,
> unless we update that class and the YAML that drives it atomically
> everywhere, we end up in a situation where the YAML does not match the
> parameterised class and causes errors.
Warning: brainstorm ahead.
As long as you c
On Aug 8, 7:51 am, Oliver Hookins wrote:
> Hi all,
>
> Recently I've hit against this problem which is proving to be a
> formidable foe. We have an in-house developed ENC and use
> parameterised classes just about everywhere and as a result enjoy a
> fairly flexible way of handing out configurat
