mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-18 19:05:06 +00:00
d44ba28d27
When running as a node, we check the `xpack.security.transport.filter.enabled` setting to see if we should create the IPFilter but this check is not really correct. The HTTP filter could be enabled or a profile filter could be enabled so there are times when we may not be filtering connections when we should. Additionally, since we do not bind the IPFilter to a null provider, Guice will try to create one during startup to inject into the security transport. This results in an exception and startup fails. This change always creates the IPFilter when running as a node. This IPFilter has its own settings and logic to determine whether it should be filtering on a given network transport. Closes elastic/elasticsearch#3592 Original commit: elastic/x-pack-elasticsearch@95c25651c4
= Elasticsearch X Plugins A set of Elastic's commercial plugins: - License - Security - Watcher - Monitoring = Setup You must checkout x-plugins and elasticsearch in the same directory as siblings. This elasticsearch checkout will be used when building x-plugins. = Build - Run unit tests: + [source, txt] ----- gradle clean test ----- - Run all tests: + [source, txt] ----- gradle clean check ----- - Run integration tests: + [source, txt] ----- gradle clean integTest ----- - Package X-Pack (wihtout running tests) + [source, txt] ----- gradle clean assemble ----- - Install X-Pack (wihtout running tests) + [source, txt] ----- gradle clean install ----- - If you don't work on the UI side of x-plugins, you can force gradle to skip building kibana by adding `xpack.kibana.build=false` to your `~/.gradle/gradle.properties`. Alternatively you add `-Pxpack.kibana.build=false` on the command line if you only want to do this on individual builds (or `-Pxpack.kibana.build=true` if you need to override having added this to your `gradle.properties`).