Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.7.0
-
Patch
Description
RangerPolicyEngineOptions has a lot of public fields, which is written from various places from the code base, which should be avoided. That object is configured from RangerConfiguration, but in the middle of the plugin initialization code, which makes this a bit more complex, than it should be.
Suggestions:
- RangerConfiguration should be treated as an object, not a static facade for a couple of config values
- RangerPolicyEngineOptions should get his configuration from directly the RangerConfiguration, in an explicit, encapsulated way.