DSL/JSON-based rules have been the way we've always done this, but as the rule expectation continue to increase in complexity, it begs the question whether a simple ruby-based module or plugin system would serve the project much better.
Examples include:
1.) I want to compare key fingerprints for all offered keys to dns key fingerprints and raise an issue
2.) I want to make it such that some encryption types are either "always required", "could be or not be there", and should never be there. It would be simply easier to make lists and move things around as the industry expectations evolve.
3.) I want to take one random element from one part of the result and compare to a completely unrelated item, that functionally allows us to build an expert system when weird things happen or we know about.
DSL/JSON-based rules have been the way we've always done this, but as the rule expectation continue to increase in complexity, it begs the question whether a simple ruby-based module or plugin system would serve the project much better.
Examples include:
1.) I want to compare key fingerprints for all offered keys to dns key fingerprints and raise an issue 2.) I want to make it such that some encryption types are either "always required", "could be or not be there", and should never be there. It would be simply easier to make lists and move things around as the industry expectations evolve. 3.) I want to take one random element from one part of the result and compare to a completely unrelated item, that functionally allows us to build an expert system when weird things happen or we know about.