WIP Accessibility palette swap

.gitignore

@@ -12,10 +12,10 @@ target
 .idea
 *.iml
 *.log
-/test/screenshots/diff
-/test/screenshots/failure
-/test/screenshots/session
-/test/screenshots/visual_regression_gallery.html
+/test/*/screenshots/diff
+/test/*/screenshots/failure
+/test/*/screenshots/session
+/test/*/screenshots/visual_regression_gallery.html
 /html_docs
 /esvm
 .htpasswd
@@ -33,5 +33,6 @@ selenium
 *.swp
 *.swo
 *.out
-ui_framework/doc_site/build/*.js*
+ui_framework/doc_site/build
+!ui_framework/doc_site/build/index.html
 yarn.lock

CONTRIBUTING.md

@@ -120,10 +120,10 @@ npm run elasticsearch
 If you're just getting started with `elasticsearch`, you could use the following command to populate your instance with a few fake logs to hit the ground running.
 
 ```bash
-npm run makelogs
+node scripts/makelogs
 ```
 
-> Make sure to execute `npm run makelogs` *after* elasticsearch is up and running!
+> Make sure to execute `node scripts/makelogs` *after* elasticsearch is up and running!
 
 Start the development server.
   ```bash
@@ -208,13 +208,13 @@ npm run test:server
 When you'd like to execute individual server-side test files, you can use the command below. Note that this command takes care of configuring Mocha with Babel compilation for you, and you'll be better off avoiding a globally installed `mocha` package. This command is great for development and for quickly identifying bugs.
 
 ```bash
-npm run mocha <file>
+node scripts/mocha <file>
 ```
 
-You could also add the `:debug` target so that `node` is run using the `--debug-brk` flag. You'll need to connect a remote debugger such as [`node-inspector`](https://github.com/node-inspector/node-inspector) to proceed in this mode.
+You could also add the `--debug` option so that `node` is run using the `--debug-brk` flag. You'll need to connect a remote debugger such as [`node-inspector`](https://github.com/node-inspector/node-inspector) to proceed in this mode.
 
 ```bash
-npm run mocha:debug <file>
+node scripts/mocha --debug <file>
 ```
 
 With `npm run test:browser`, you can run only the browser tests. Coverage reports are available for browser tests by running `npm run test:coverage`. You can find the results under the `coverage/` directory that will be created upon completion.
@@ -265,7 +265,7 @@ npm run test:ui
 ```
 
 
-In order to start the server required for the `test:ui:runner` tasks, use the following command. Once the server is started `test:ui:runner` can be run multiple times without waiting for the server to start.
+In order to start the server required for the `node scripts/functional_test_runner` tasks, use the following command. Once the server is started `node scripts/functional_test_runner` can be run multiple times without waiting for the server to start.
 
 ```bash
 npm run test:ui:server
@@ -274,7 +274,7 @@ npm run test:ui:server
 To execute the front-end browser tests, enter the following. This requires the server started by the `test:ui:server` task.
 
 ```bash
-npm run test:ui:runner
+node scripts/functional_test_runner
 ```
 
 To filter these tests, use `--grep=foo` for only running tests that match a regular expression.
@@ -294,7 +294,7 @@ export TEST_ES_HOSTNAME=aaa5d22032d76805fcce724ed9d9f5a2.us-east-1.aws.found.io
 export TEST_ES_PORT=9200
 export TEST_ES_USER=elastic
 export TEST_ES_PASS=<your password here>
-npm run test:ui:runner
+node scripts/functional_test_runner
 ```
 
 ##### Browser Automation Notes

Gruntfile.js

@@ -12,7 +12,6 @@ module.exports = function (grunt) {
     plugins: __dirname + '/src/core_plugins',
     server: __dirname + '/src/server',
     target: __dirname + '/target', // location of the compressed build targets
-    testUtilsDir: __dirname + '/src/test_utils',
     configFile: __dirname + '/src/config/kibana.yml',
 
     karmaBrowser: (function () {

README.md

@@ -1,4 +1,4 @@
-# Kibana 6.0.0-alpha1
+# Kibana 6.0.0-alpha2
 
 Kibana is your window into the [Elastic Stack](https://www.elastic.co/products). Specifically, it's
 an open source ([Apache Licensed](LICENSE.md)),
@@ -40,14 +40,13 @@ out an open PR:
 
 ### Snapshot Builds
 
-For the daring, snapshot builds are available. These builds are created nightly and have undergone no formal QA, so they should never be run in production.
+For the daring, snapshot builds are available. These builds are created nightly and have undergone no formal QA, so they should never be run in production. All builds are 64 bit.
 
 | platform |  |
 | --- | --- |
-| OSX | [tar](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-darwin-x86_64.tar.gz) |
-| Linux x64 | [tar](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-linux-x86_64.tar.gz) [deb](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-amd64.deb) [rpm](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-x86_64.rpm) |
-| Linux x86 | [tar](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-linux-x86.tar.gz) [deb](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-i386.deb) [rpm](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-i686.rpm) |
-| Windows | [zip](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha1-SNAPSHOT-windows-x86.zip) |
+| OSX | [tar](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha2-SNAPSHOT-darwin-x86_64.tar.gz) |
+| Linux | [tar](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha2-SNAPSHOT-linux-x86_64.tar.gz) [deb](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha2-SNAPSHOT-amd64.deb) [rpm](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha2-SNAPSHOT-x86_64.rpm) |
+| Windows | [zip](https://snapshots.elastic.co/downloads/kibana/kibana-6.0.0-alpha2-SNAPSHOT-windows-x86_64.zip) |
 
 ## Documentation
 

bin/kibana

@@ -21,4 +21,4 @@ if [ ! -x "$NODE" ]; then
   exit 1
 fi
 
-exec "${NODE}" $NODE_OPTIONS --no-warnings "${DIR}/src/cli" ${@}
+NODE_ENV=production exec "${NODE}" $NODE_OPTIONS --no-warnings "${DIR}/src/cli" ${@}

bin/kibana-plugin

@@ -21,4 +21,4 @@ if [ ! -x "$NODE" ]; then
   exit 1
 fi
 
-exec "${NODE}" $NODE_OPTIONS --no-warnings "${DIR}/src/cli_plugin" "$@"
+NODE_ENV=production exec "${NODE}" $NODE_OPTIONS --no-warnings "${DIR}/src/cli_plugin" "$@"

bin/kibana-plugin.bat

@@ -7,6 +7,8 @@ for %%I in ("%SCRIPT_DIR%..") do set DIR=%%~dpfI
 
 set NODE=%DIR%\node\node.exe
 
+set NODE_ENV="production"
+
 WHERE /Q node
 IF %ERRORLEVEL% EQU 0 (
   for /f "delims=" %%i in ('WHERE node') do set SYS_NODE=%%i

bin/kibana.bat

@@ -7,6 +7,8 @@ for %%I in ("%SCRIPT_DIR%..") do set DIR=%%~dpfI
 
 set NODE=%DIR%\node\node.exe
 
+set NODE_ENV="production"
+
 WHERE /Q node
 IF %ERRORLEVEL% EQU 0 (
   for /f "delims=" %%i in ('WHERE node') do set SYS_NODE=%%i

docs/development/core/development-modules.asciidoc

@@ -38,9 +38,7 @@ Kibana uses Webpack to bundle Kibana's dependencies.
 
 Here is how import/require statements are resolved to a file:
 
-NOTE: if you're familiar with the node.js algorithm, the changes are in *2.ii* and *3.i.f* to *3.i.g*
-
-. Pick an algorithm
+. Check the beginning of the module path  
   * if the path starts with a '.'
     ** append it the directory of the current file
     ** proceed to *3*

docs/getting-started/tutorial-load-dataset.asciidoc

@@ -4,7 +4,7 @@
 The tutorials in this section rely on the following data sets:
 
 * The complete works of William Shakespeare, suitably parsed into fields. Download this data set by clicking here:
-  https://download.elastic.co/demos/kibana/gettingstarted/shakespeare.json[shakespeare.json].
+  https://download.elastic.co/demos/kibana/gettingstarted/shakespeare_6.0.json[shakespeare.json].
 * A set of fictitious accounts with randomly generated data. Download this data set by clicking here:
   https://download.elastic.co/demos/kibana/gettingstarted/accounts.zip[accounts.zip]
 * A set of randomly generated log files. Download this data set by clicking here:
@@ -60,36 +60,35 @@ field's searchability or whether or not it's _tokenized_, or broken up into sepa
 
 Use the following command in a terminal (eg `bash`) to set up a mapping for the Shakespeare data set:
 
-[source,shell]
-curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/shakespeare -d '
+[source,js]
+PUT /shakespeare
 {
- "mappings" : {
-  "_default_" : {
-   "properties" : {
-    "speaker" : {"type": "string", "index" : "not_analyzed" },
-    "play_name" : {"type": "string", "index" : "not_analyzed" },
-    "line_id" : { "type" : "integer" },
-    "speech_number" : { "type" : "integer" }
+ "mappings": {
+  "doc": {
+   "properties": {
+    "speaker": {"type": "keyword"},
+    "play_name": {"type": "keyword"},
+    "line_id": {"type": "integer"},
+    "speech_number": {"type": "integer"}
    }
   }
  }
 }
-';
+
+//CONSOLE
 
 This mapping specifies the following qualities for the data set:
 
-* The _speaker_ field is a string that isn't analyzed. The string in this field is treated as a single unit, even if
-there are multiple words in the field.
-* The same applies to the _play_name_ field.
+* Because the _speaker_ and _play_name_ fields are keyword fields, they are not analyzed. The strings are treated as a single unit even if they contain multiple words.
 * The _line_id_ and _speech_number_ fields are integers.
 
 The logs data set requires a mapping to label the latitude/longitude pairs in the logs as geographic locations by
 applying the `geo_point` type to those fields.
 
 Use the following commands to establish `geo_point` mapping for the logs:
 
-[source,shell]
-curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-2015.05.18 -d '
+[source,js]
+PUT /logstash-2015.05.18
 {
   "mappings": {
     "log": {
@@ -105,10 +104,11 @@ curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-20
     }
   }
 }
-';
 
-[source,shell]
-curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-2015.05.19 -d '
+//CONSOLE
+
+[source,js]
+PUT /logstash-2015.05.19
 {
   "mappings": {
     "log": {
@@ -124,10 +124,11 @@ curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-20
     }
   }
 }
-';
 
-[source,shell]
-curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-2015.05.20 -d '
+//CONSOLE
+
+[source,js]
+PUT /logstash-2015.05.20
 {
   "mappings": {
     "log": {
@@ -143,22 +144,25 @@ curl -H 'Content-Type: application/json' -XPUT http://localhost:9200/logstash-20
     }
   }
 }
-';
+
+//CONSOLE
 
 The accounts data set doesn't require any mappings, so at this point we're ready to use the Elasticsearch
 {es-ref}docs-bulk.html[`bulk`] API to load the data sets with the following commands:
 
 [source,shell]
 curl -H 'Content-Type: application/x-ndjson' -XPOST 'localhost:9200/bank/account/_bulk?pretty' --data-binary @accounts.json
-curl -H 'Content-Type: application/x-ndjson' -XPOST 'localhost:9200/shakespeare/_bulk?pretty' --data-binary @shakespeare.json
+curl -H 'Content-Type: application/x-ndjson' -XPOST 'localhost:9200/shakespeare/doc/_bulk?pretty' --data-binary @shakespeare_6.0.json
 curl -H 'Content-Type: application/x-ndjson' -XPOST 'localhost:9200/_bulk?pretty' --data-binary @logs.jsonl
 
 These commands may take some time to execute, depending on the computing resources available.
 
 Verify successful loading with the following command:
 
-[source,shell]
-curl 'localhost:9200/_cat/indices?v'
+[source,js]
+GET /_cat/indices?v
+
+//CONSOLE
 
 You should see output similar to the following:
 

docs/index.asciidoc

@@ -4,7 +4,7 @@
 //////////
 release-state can be: released | prerelease | unreleased
 //////////
-:release-state:  unreleased
+:release-state:  prerelease
 :version:        6.0.0-alpha1
 :major-version:  6.x
 :branch:         master
@@ -44,3 +44,5 @@ include::plugins.asciidoc[]
 include::development.asciidoc[]
 
 include::limitations.asciidoc[]
+
+include::release-notes.asciidoc[]

docs/management/advanced-options.asciidoc

@@ -33,6 +33,7 @@ adapt to the interval between measurements. Keys are http://en.wikipedia.org/wik
 `metaFields`:: An array of fields outside of `_source`. Kibana merges these fields into the document when displaying the
 document.
 `discover:sampleSize`:: The number of rows to show in the Discover table.
+`discover:aggs:terms:size`:: Determines how many terms will be visualized when clicking the "visualize" button, in the field drop downs, in the discover sidebar. The default value is `20`. 
 `doc_table:highlight`:: Highlight results in Discover and Saved Searches Dashboard. Highlighting makes request slow when
 working on big documents. Set this property to `false` to disable highlighting.
 `doc_table:highlight:all_fields`:: Improves highlighting by using a separate `highlight_query` that uses `all_fields` mode on

docs/migration/migrate_6_0.asciidoc

@@ -4,6 +4,7 @@
 This section discusses the changes that you need to be aware of when migrating
 your application to Kibana 6.0.
 
+
 [float]
 === Removed option to use unsupported scripting languages
 *Details:* Kibana 5.x allowed users to create scripted fields using any scripting language enabled in Elasticsearch.
@@ -12,6 +13,7 @@ Kibana 6.0 will only support Painless and Lucene expression based scripts.
 
 *Impact:* You will need to migrate your groovy, python, javascript, etc. scripted fields to Painless or Lucene expressions.
 
+
 [float]
 === Changed response format of status API
 *Details:* In an effort to align with our style guidelines and provide a digestible response,
@@ -22,10 +24,31 @@ the status API has changed:
 
 *Impact:* You will need to update anything using the status API and expecting the previous response format.
 
+
 [float]
 === Timelion requires comma to separate queries
-*Details:* Kibana 5.x allowed users to use spaces as a query separator in timelion `.es(400) .es(500)`. 
+*Details:* Kibana 5.x allowed users to use spaces as a query separator in timelion `.es(400) .es(500)`.
 This is no longer the case. Now, only commas are a valid query separator: e.g. `.es(400), .es(500)`
 
-
 *Impact:* You will need to migrate your stored timelion queries to the new syntax.
+
+
+[float]
+=== Requires 64 bit operating system
+*Details:* Kibana 6.0.0 and onward only support 64 bit operating systems.
+
+*Impact:* You will need to install Kibana 6.x on a 64 bit operating system. No extra data migration steps are necessary when moving from 32 bit to 64 bit.
+
+
+[float]
+=== NODE_ENV no longer has an impact on Kibana
+*Details:* Setting the NODE_ENV environment variable can break Kibana processes in unexpected ways, which is especially unfortunate since it is a common environment variable to have configured on a system, and you wouldn't expect it to break anything in Kibana. Kibana will now effectively ignore NODE_ENV entirely.
+
+*Impact:* If you're developing a custom plugin that depends on NODE_ENV, you will need to update it to use a different, custom environment variable.
+
+
+[float]
+=== Kibana 4.x configuration names using `_` instead of `.` have been removed
+*Details:* In Kibana 4.2, we renamed all configuration names in kibana.yml to use `.` as a separator instead of `_`, though the legacy configurations would still continue to work. In 5.0, we started logging deprecation notices whenever the legacy configurations were encountered. In 6.0 onward, legacy configuration names that use an underscore instead of a dot will no longer work.
+
+*Impact:* Any usages of underscore separated configuration names in kibana.yml need to be updated to their modern equivalents. See <<settings,Configuring Kibana>> for accepted configurations.

docs/release-notes.asciidoc

@@ -0,0 +1,11 @@
+[[release-notes]]
+= Release Notes
+
+[partintro]
+--
+This section summarizes the changes in each release.
+
+* <<release-notes-6.0.0-alpha1>>
+
+--
+include::release-notes/6.0.0-alpha1.asciidoc[]