Merge branch 'master' into node-version-validator-elastic#12976

Author: mistic

docs/discover/context.asciidoc

@@ -32,7 +32,7 @@ pattern the context is based on.
 
 While not required, it is recommended to only
 use fields which have {ref}/doc-values.html[doc values] enabled to achieve
-good performance and avoid unnecessary {ref}/modules-fielddata.html[field 
+good performance and avoid unnecessary {ref}/modules-fielddata.html[field
 data] usage. Common examples for suitable fields include log line numbers,
 monotonically increasing counters and high-precision timestamps.
 --
@@ -43,6 +43,8 @@ NOTE: The number of documents displayed by default can be configured
 via the `context:defaultSize` setting in <<advanced-options, *Management >
 Advanced Settings*>>.
 
+[float]
+[[change-context-size]]
 === Changing the Context Size
 
 You can change the number documents displayed before and after the anchor
@@ -66,6 +68,8 @@ NOTE: The default number of documents loaded with each button click can be
 configured via the `context:step` setting in <<advanced-options, *Management >
 Advanced Settings*>>.
 
+[float]
+[[filter-context]]
 === Filtering the Context
 
 Depending on how the documents are partitioned into index patterns, the context

docs/plugins.asciidoc

@@ -15,7 +15,7 @@ The Kibana plugin interfaces are in a state of constant development.  We cannot
 ==============================================
 --
 
-[[_installing_plugins]]
+[[install-plugin]]
 == Installing Plugins
 
 Use the following command to install a plugin:
@@ -82,6 +82,7 @@ You can specify the environment variable directly when installing plugins:
 $ http_proxy="http://proxy.local:4242" bin/kibana-plugin install <package name or URL>
 
 
+[[update-remove-plugin]]
 == Updating & Removing Plugins
 
 To update a plugin, remove the current version and reinstall the plugin.
@@ -95,6 +96,7 @@ You can also remove a plugin manually by deleting the plugin's subdirectory unde
 
 NOTE: Removing a plugin will result in an "optimize" run which will delay the next start of Kibana.
 
+[[disable-plugin]]
 == Disabling Plugins
 
 Use the following command to disable a plugin:
@@ -108,6 +110,7 @@ NOTE: Disabling or enabling a plugin will result in an "optimize" run which will
 
 <1> You can find a plugin's plugin ID as the value of the `name` property in the plugin's `package.json` file.
 
+[[configure-plugin-manager]]
 == Configuring the Plugin Manager
 
 By default, the plugin manager provides you with feedback on the status of the activity you've asked the plugin manager

docs/setup/docker.asciidoc

@@ -7,6 +7,8 @@ A list of all published Docker images and tags can be found at
 https://www.docker.elastic.co[www.docker.elastic.co]. The source code can be
 found on https://github.com/elastic/kibana-docker/tree/{branch}[GitHub].
 
+[float]
+[[image-type]]
 === Image types
 
 These images are free to use under the Elastic license. They contain open source 
@@ -19,6 +21,8 @@ Elastic license levels.
 Alternatively, you can download `-oss` images, which contain only features that 
 are available under the Apache 2.0 license.
 
+[float]
+[[pull-image]]
 === Pulling the image
 Obtaining Kibana for Docker is as simple as issuing a +docker pull+ command
 against the Elastic Docker registry.
@@ -42,14 +46,17 @@ docker pull {docker-repo}-oss:{version}
 
 endif::[]
 
+[float]
+[[configuring-kibana-docker]]
 === Configuring Kibana on Docker
 
 The Docker images provide several methods for configuring Kibana. The
 conventional approach is to provide a `kibana.yml` file as described in
 {kibana-ref}/settings.html[Configuring Kibana], but it's also possible to use
 environment variables to define settings.
 
-[[docker-bind-mount-config]]
+[float]
+[[bind-mount-config]]
 ==== Bind-mounted configuration
 
 One way to configure Kibana on Docker is to provide `kibana.yml` via bind-mounting.
@@ -65,7 +72,8 @@ services:
       - ./kibana.yml:/usr/share/kibana/config/kibana.yml
 --------------------------------------------
 
-[[docker-env-config]]
+[float]
+[[environment-variable-config]]
 ==== Environment variable configuration
 
 Under Docker, Kibana can be configured via environment variables. When
@@ -106,6 +114,8 @@ services:
 Since environment variables are translated to CLI arguments, they take
 precedence over settings configured in `kibana.yml`.
 
+[float]
+[[docker-defaults]]
 ==== Docker defaults
 The following settings have different default values when using the Docker
 images:
@@ -123,8 +133,8 @@ In the {xpack} image, the following additional defaults are also set:
 `xpack.monitoring.ui.container.elasticsearch.enabled`:: `true`
 
 These settings are defined in the default `kibana.yml`. They can be overridden
-with a <<docker-bind-mount-config,custom `kibana.yml`>> or via
-<<docker-env-config,environment variables>>.
+with a <<bind-mount-config,custom `kibana.yml`>> or via
+<<environment-variable-config,environment variables>>.
 
 IMPORTANT: If replacing `kibana.yml` with a custom version, be sure to copy the
 above defaults to the custom file if you want to retain them. If not, they will

docs/setup/production.asciidoc

@@ -40,42 +40,7 @@ For information about setting up Kibana users, see
 [[enabling-ssl]]
 === Enabling SSL
 
-Kibana supports TLS/SSL encryption for both client requests and the requests the 
-Kibana server sends to Elasticsearch.
-
-To encrypt communications between the browser and the Kibana server, you configure the `server.ssl.enabled`,
-`server.ssl.certificate` and `server.ssl.key` properties in `kibana.yml`:
-
-[source,text]
-----
-# SSL for outgoing requests from the Kibana Server (PEM formatted)
-server.ssl.enabled: true
-server.ssl.key: /path/to/your/server.key
-server.ssl.certificate: /path/to/your/server.crt
-----
-
-If you are using {security} or a proxy that provides an HTTPS endpoint for Elasticsearch,
-you can configure Kibana to access Elasticsearch via HTTPS so communications between
-the Kibana server and Elasticsearch are encrypted.
-
-To do this, you specify the HTTPS
-protocol when you configure the Elasticsearch URL in `kibana.yml`:
-
-[source,text]
-----
-elasticsearch.url: "https://<your_elasticsearch_host>.com:9200"
-----
-
-If you are using a self-signed certificate for Elasticsearch, set the `certificateAuthorities` property in
-`kibana.yml` to specify the location of the PEM file. Setting the `certificateAuthorities` property lets you use the
-default `verificationMode` option of `full`.
-
-[source,text]
-----
-# If you need to provide a CA certificate for your Elasticsearch instance, put
-# the path of the pem file here.
-elasticsearch.ssl.certificateAuthorities: [ "/path/to/your/ca/cacert.pem" ]
-----
+See <<configuring-tls>>. 
 
 [float]
 [[load-balancing]]

docs/setup/settings.asciidoc

@@ -5,7 +5,8 @@ The Kibana server reads properties from the `kibana.yml` file on startup. The de
 on `localhost:5601`. To change the host or port number, or connect to Elasticsearch running on a different machine,
 you'll need to update your `kibana.yml` file. You can also enable SSL and set a variety of other options. Finally, environment variables can be injected into configuration using `${MY_ENV_VAR}` syntax.
 
-Kibana Configuration Settings
+.Kibana Configuration Settings
+
 `console.enabled:`:: *Default: true* Set to false to disable Console.  Toggling this will cause the server to regenerate assets on the next startup, which may cause a delay before pages start being served.
 
 `cpu.cgroup.path.override:`:: Override for cgroup cpu path when mounted in manner that is inconsistent with `/proc/self/cgroup`

docs/visualize/tilemap.asciidoc

@@ -7,10 +7,14 @@ NOTE: By default, Kibana uses the https://www.elastic.co/elastic-maps-service[El
 to display map tiles. To use other tile service providers, configure the <<tilemap-settings,tilemap settings>>
 in `kibana.yml`.
 
+[float]
+[[configuration]]
 === Configuration
 
+[float]
 ==== Data
 
+[float]
 ===== Metrics
 
 The default _metrics_ aggregation for a coordinate map is the *Count* aggregation. You can select any of the following
@@ -31,6 +35,7 @@ the number of unique values in a field. Select a field from the drop-down.
 
 Enter a string in the *Custom Label* field to change the display label.
 
+[float]
 ===== Buckets
 
 Coordinate maps use the {ref}/search-aggregations-bucket-geohashgrid-aggregation.html[_geohash_] aggregation. Select a field, typically coordinates, from the
@@ -66,6 +71,7 @@ NOTE: In Elasticsearch releases 1.4.3 and later, this functionality requires you
 
 The availability of these options varies depending on the aggregation you choose.
 
+[float]
 ==== Options
 
 
@@ -98,8 +104,7 @@ After changing options, click the  *Apply changes* button to update your visuali
 changes* button to keep your visualization in its current state.
 
 [float]
-[[navigating-map]]
-
+[[navigate-map]]
 === Navigating the Map
 
 Once your tilemap visualization is ready, you can explore the map in several ways:

docs/visualize/time-series-visual-builder.asciidoc

@@ -10,6 +10,7 @@ aggregations and pipeline aggregations to display complex data in a meaningful w
 
 image:images/tsvb-screenshot.png["Time Series Visual Builder Interface"]
 
+[[time-series-visualizations]]
 === Featured Visualizations
 
 Time Series Visual Build comes with 6 different visualization types. You can
@@ -73,6 +74,7 @@ You define which field group to show in the rows and what columns of data to dis
 image:images/tsvb-table.png["Table Visualization"]
 
 
+[[time-series-interface]]
 === Interface Overview
 
 The user interface for each visualization is compose of a "Data" tab and "Panel

docs/visualize/xychart.asciidoc

@@ -33,11 +33,14 @@ NOTE: In Elasticsearch releases 1.4.3 and later, this functionality requires you
 
 The availability of these options varies depending on the aggregation you choose.
 
+[float]
+[[metrics-axes]]
 === Metrics & Axes
 
 Select the *Metrics & Axes* tab to change the way each individual metric is shown on the chart.
 The data series are styled in the _Metrics_ section, while the axes are styled in the X and Y axis sections.
 
+[float]
 ==== Metrics
 Modify how each metric from the Data panel is visualized on the chart.
 
@@ -46,6 +49,7 @@ Modify how each metric from the Data panel is visualized on the chart.
 *Value Axis*:: choose the axis you want to plot this data too (the properties of each are configured under Y-axes).
 *Line mode*:: should the outline of lines or bars appear *smooth*, *straight*, or *stepped*.
 
+[float]
 ==== Y-axis
 
 Style all the Y-axes of the chart.
@@ -61,6 +65,7 @@ Style all the Y-axes of the chart.
                            this box to change both upper and lower bounds to match the values returned in the data.
 *Custom Extents*:::: You can define custom minimum and maximum for each axis
 
+[float]
 ==== X-Axis
 
 *Position*:: position of the X-Axis (*left* or *right* for horizontal charts, and *top* or *bottom* for vertical charts).
@@ -70,16 +75,19 @@ Style all the Y-axes of the chart.
 *Labels - Rotate*:::: You can enter the number in degrees for how much you want to rotate labels
 *Labels - Truncate*:::: You can enter the size in pixels to which the label is truncated
 
-
+[float]
+[[panel-settings]]
 === Panel Settings
 
 These are options that apply to the entire chart and not just the individual data series.
 
+[float]
 ==== Common options
 *Legend Position*:: Move your legend to the *left*, *right*, *top* or *bottom*
 *Show Tooltip*:: Enables or disables the display of tooltip on hovering over chart objects
 *Current Time Marker*:: Show a line indicating the current time
 
+[float]
 ==== Grid options
 You can enable grid on the chart. By default grid is displayed on the category axis only.
 

package.json

@@ -61,8 +61,8 @@
     "debug-break": "node --nolazy --inspect-brk scripts/kibana --dev",
     "precommit": "node scripts/precommit_hook",
     "karma": "karma start",
-    "lint": "echo 'use `node scripts/eslint`' && false",
-    "lintroller": "echo 'use `node scripts/eslint --fix`' && false",
+    "lint": "echo 'use `node scripts/eslint` and/or `node scripts/tslint`' && false",
+    "lintroller": "echo 'use `node scripts/eslint --fix` and/or `node scripts/tslint --fix`' && false",
     "makelogs": "echo 'use `node scripts/makelogs`' && false",
     "mocha": "echo 'use `node scripts/mocha`' && false",
     "sterilize": "grunt sterilize",
@@ -226,7 +226,11 @@
     "@kbn/eslint-plugin-license-header": "link:packages/kbn-eslint-plugin-license-header",
     "@kbn/plugin-generator": "link:packages/kbn-plugin-generator",
     "@kbn/test": "link:packages/kbn-test",
-    "@types/globby": "^6.1.0",
+    "@types/eslint": "^4.16.2",
+    "@types/execa": "^0.9.0",
+    "@types/getopts": "^2.0.0",
+    "@types/glob": "^5.0.35",
+    "@types/listr": "^0.13.0",
     "@types/minimatch": "^2.0.29",
     "angular-mocks": "1.4.7",
     "babel-eslint": "8.1.2",
@@ -283,6 +287,7 @@
     "karma-safari-launcher": "1.0.0",
     "leadfoot": "1.7.5",
     "license-checker": "^16.0.0",
+    "listr": "^0.14.1",
     "load-grunt-config": "0.19.2",
     "makelogs": "^4.0.5",
     "marked-text-renderer": "0.1.0",
@@ -305,6 +310,9 @@
     "ts-jest": "^22.4.6",
     "ts-loader": "^3.5.0",
     "ts-node": "^6.0.3",
+    "tslint": "^5.10.0",
+    "tslint-config-prettier": "^1.12.0",
+    "tslint-plugin-prettier": "^1.3.0",
     "typescript": "^2.8.3",
     "vinyl-fs": "^3.0.2",
     "xml2js": "^0.4.19",

packages/kbn-dev-utils/index.d.ts

@@ -0,0 +1,18 @@
+import { Readable } from 'stream';
+
+type LogLevel = 'silent' | 'error' | 'warning' | 'info' | 'debug' | 'verbose';
+
+export class ToolingLog extends Readable {
+  public verbose(...args: any[]): void;
+  public debug(...args: any[]): void;
+  public info(...args: any[]): void;
+  public success(...args: any[]): void;
+  public warning(...args: any[]): void;
+  public error(errOrMsg: string | Error): void;
+  public write(...args: any[]): void;
+  public indent(spaces: number): void;
+  public getLevel(): LogLevel;
+  public setLevel(level: LogLevel): void;
+}
+
+export function createToolingLog(level?: LogLevel): ToolingLog;

packages/kbn-dev-utils/tsconfig.json

@@ -0,0 +1,6 @@
+{
+  "extends": "../../tsconfig.json",
+  "include": [
+    "index.d.ts"
+  ],
+}

packages/kbn-pm/tslint.yaml

@@ -0,0 +1,19 @@
+extends: ../../tslint.yaml
+
+rules:
+  max-classes-per-file: false
+  interface-name: false
+  variable-name: false
+  no-empty: false
+  object-literal-sort-keys: false
+  member-ordering: false
+  no-console: false
+  only-arrow-functions: false
+  no-shadowed-variable: false
+  no-empty-interface: false
+  ordered-imports: false
+  interface-over-type-literal: false
+  prettier: false
+  prefer-const: false
+  member-access: false
+  no-unused-variable: false

packages/kbn-system-loader/tslint.yaml

@@ -0,0 +1,14 @@
+extends: ../../tslint.yaml
+
+rules:
+  max-classes-per-file: false
+  interface-name: false
+  variable-name: false
+  no-empty: false
+  object-literal-sort-keys: false
+  member-ordering: false
+  member-access: false
+  ordered-imports: false
+  interface-over-type-literal: false
+  array-type: false
+  prefer-const: false

scripts/tslint.js

@@ -0,0 +1,2 @@
+require('../src/babel-register');
+require('../src/dev/tslint').runTslintCli();