mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-09 14:34:43 +00:00
ce496938cd
Currently there are a number of helper methods, all used at various stages of initializing xpack, for reading "enabled" settings. Almost all of these read the setting directly rather than use the new settings infra. This change adds an XPackSettings class to contain these settings constants, and adds all the enabled settings to it. Note: While there is an existing MonitoringSettings, I think we do not have enough settings (especially for all features) to warrant a separate class per "feature" (eg graph would have nothing). We should decide if/when this is necessary on a case by case basis, but I think the enabled settings should all go here in XPackSettings. Original commit: elastic/x-pack-elasticsearch@086152d5a5
= 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`).