mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 04:58:50 +00:00
javanna
0504f02026
inclusions and exclusions shouldn't be considered wildcard expressions
The security indices resolver checks through an assertion that shard level requests always have their wildcard expressions resolved. Index names that start with `-` or `+` though shouldn't be considered wild card expressions. Up to 6.x there can be indices with names starting with `-` or `+` and we have to take that into account. Also moved from assertion to explicit exception so we can also test it better. Original commit: elastic/x-pack-elasticsearch@a520bbf247
= 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`).
Description
Languages
Java
99.5%
Groovy
0.4%