Hi,
one concern I have is maintainability. Scripts tend to go out of date
and my question would be how we can detect this when it happens. As for
the example with the index consistency check you mentioned, I'm
wondering why this is implemented as a script instead of plain Java. I'd
say if we consider this an important functionality that should be added
to Oak, then it is probably better to integrate it better, with tests,
documentation, etc.
Regards
Marcel
On 13/04/17 07:05, Chetan Mehrotra wrote:
Hi Team,
We have few oak-run console groovy scripts used often to
analyze/troubleshoot customer setups. Currently these are scattered
across various github gist.
I propose that we
1. Create a new module oak-run-scripts (or oak-console-scripts) and
host such generic scripts there. 2. This module would not be part of
build
3. Scripts present here would be generic i.e. not tied to any product
Thoughts?
Chetan Mehrotra
