The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.
The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.
flush,weight on resolution is are private in facter 3
The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.
value, name, execute,flush, weight on resolution are private in facter 3
The Exception Execution module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes.
value, name, execute, flush, weight on resolution are private in facter 3
Trying to hide some of the Execution module functions, break the LegacyFacter::Util::Config unit tests, because they use the with_env function. The same thing is valid for the Fact, Resolution and Aggregate classes. If we use access proxies we need to make sure that methods like define_resolution return the proxy. All of this makes the code harder to understand and there's little advantage added.