GitLab

Singletons are a very bad idea when we need to start-up several ES nodes
within one JVM, as we do in unit tests. This once again made problems
where the RepositoriesService suddenly believed it would be executing on
a non-master node even though it was executing on a master node.

The org.codelibs.elasticsearch.module.lang-painless does not work any
more with ES 7.12.x.

Only this package actually made the Painless plugin available as Maven
dependency. elasticsearch-scripting-painless-spi only makes the SPI
available without packaging the actual plugin.

So, right now we have no dependency to get Painless for unit tests.

In "normal" ES setups, Painless within Signals should continue to work.

The org.codelibs.elasticsearch.module.lang-painless does not work any
more with ES 7.12.x. So, right now we have no dependency to get Painless
for unit tests.

In "normal" ES setups, Painless within Signals should continue to work.

- Made operations slightly more synchronous to better handle race
conditions
- Watch log now lists document version of watch

This avoids immediate throttling or similar phenomenons when watch with
same name is re-created

- make sure that watch state always includes node name
- support for multiple nodes in unit tests

- More robust against port collisions
- More control over single nodes (can be started/stopped at will)

It is important that the SchedulerThread and the worker threads are in
the same thread group as the initializing thread. Otherwise, using the
nodeClient will hit SecurityExceptions when making calls into ES.

In the long run, this shall replace RestHelper

Command:

$:~/git/search-guard-suite$ mvn license:aggregate-add-third-party