Update With Saved Object Client changes

.gitignore

@@ -42,3 +42,4 @@ package-lock.json
 .vscode
 npm-debug.log*
 .tern-project
+index.css

README.md

@@ -71,7 +71,7 @@ _Note: The version numbers below are only examples, meant to illustrate the rela
 
 ## Questions? Problems? Suggestions?
 
-- If you've found a bug or want to request a feature, please create a [GitHub Issue](https://github.com/elastic/kibana/issues/new/choose).
+- If you've found a bug or want to request a feature, please create a [GitHub Issue](https://github.com/elastic/kibana/issues/new).
 Please check to make sure someone else hasn't already created an issue for the same topic.
 - Need help using Kibana? Ask away on our [Kibana Discuss Forum](https://discuss.elastic.co/c/kibana) and a fellow community member or
 Elastic engineer will be glad to help you out.

config/kibana.yml

@@ -109,6 +109,5 @@
 # metrics. Minimum is 100ms. Defaults to 5000.
 #ops.interval: 5000
 
-# The default locale. This locale can be used in certain circumstances to substitute any missing
-# translations.
-#i18n.defaultLocale: "en"
+# Specifies locale to be used for all localizable strings, dates and number formats.
+#i18n.locale: "en"

docs/migration/migrate_7_0.asciidoc

@@ -4,7 +4,7 @@
 This section discusses the changes that you need to be aware of when migrating
 your application to Kibana 7.0.
 
-See also <<release-highlights>> and <<release-notes>>. 
+See also <<release-highlights>> and <<release-notes>>.
 
 [float]
 === Removed support for tribe nodes
@@ -23,11 +23,11 @@ Kibana 7.0 will only use the Node.js distribution included in the package.
 [float]
 === Advanced setting query:queryString:options no longer applies to filters
 *Details:* In previous versions of Kibana the Advanced Setting `query:queryString:options` was applied to both queries
-and custom filters using the `query_string` query. This could cause errors if a custom filter used options that 
+and custom filters using the `query_string` query. This could cause errors if a custom filter used options that
 conflicted with the Advanced Setting. In 7.0 `query:queryString:options` will no longer be applied to filters so that
 users can have full control over their custom filters.
 
-*Impact:* You must ensure that any saved searches with a `query_string` filter aren't relying implicitly on 
+*Impact:* You must ensure that any saved searches with a `query_string` filter aren't relying implicitly on
 `query:queryString:options`.
 
 [float]
@@ -41,4 +41,12 @@ so we no longer need this workaround.
 *Impact:* Since we'll no longer send the `default_field` parameter in Kibana's query_string query, Elasticsearch
 will use the index setting instead. The default for the index setting is also `*`, so most users should not be impacted.
 If some of your indices have a non-default `default_field` setting, you may want to update it or re-add the parameter
-to Kibana's advanced setting.
+to Kibana's advanced setting.
+
+[float]
+=== Deprecated kibana.yml setting `xpack.monitoring.node_resolver` has been removed
+*Details:* This setting has been deprecated since 5.6, when it was explicitly recommended to use `uuid` as its value.
+
+*Impact:* This setting is no longer necessary. If you enable {monitoring} across the Elastic Stack, a monitoring agent runs
+on each Elasticsearch node, Logstash node, Kibana instance, and Beat to collect and index metrics. Each node and instance is
+considered unique based on its persistent UUID, which is written to the path.data directory when the node or instance starts.

docs/ml/creating-jobs.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[ml-jobs]]
-== Creating Machine Learning Jobs
+== Creating machine learning jobs
 
 Machine learning jobs contain the configuration information and metadata
 necessary to perform an analytics task.

docs/ml/job-tips.asciidoc

@@ -1,24 +1,28 @@
 [role="xpack"]
 [[job-tips]]
-=== Machine Learning Job Tips
+=== Machine learning job tips
 ++++
-<titleabbrev>Job Tips</titleabbrev>
+<titleabbrev>Job tips</titleabbrev>
 ++++
 
 When you are creating a job in {kib}, the job creation wizards can provide
 advice based on the characteristics of your data. By heeding these suggestions,
 you can create jobs that are more likely to produce insightful {ml} results.
 
 [[bucket-span]]
-==== Bucket Span
+==== Bucket span
 
 The bucket span is the time interval that {ml} analytics use to summarize and
 model data for your job. When you create a job in {kib}, you can choose to
-estimate a bucket span value based on your data characteristics. Typically, the
-estimated value is between 5 minutes to 1 hour. If you choose a value that is
-larger than one day or is significantly different than the estimated value, you
-receive an informational message. For more information about choosing an
-appropriate bucket span, see {xpack-ref}/ml-buckets.html[Buckets].
+estimate a bucket span value based on your data characteristics. 
+
+NOTE: The bucket span must contain a valid time interval. For more information, 
+see {ref}/ml-job-resource.html#ml-analysisconfig[Analysis configuration objects].
+
+If you choose a value that is larger than one day or is significantly different 
+than the estimated value, you receive an informational message. For more 
+information about choosing an appropriate bucket span, see 
+{xpack-ref}/ml-buckets.html[Buckets].
 
 [[cardinality]]
 ==== Cardinality
@@ -30,16 +34,26 @@ detect when users are accessing resources differently than they usually do.
 
 If the field that you use to split your data has many different values, the
 job uses more memory resources. In particular, if the cardinality of the
-`partition_field_name` is greater than 100, you are advised to consider
-alternative options such as population analysis.
+`by_field_name`, `over_field_name`, or `partition_field_name` is greater than 
+1000, you are advised that there might be high memory usage. 
 
 Likewise if you are performing population analysis and the cardinality of the
 `over_field_name` is below 10, you are advised that this might not be a suitable
-field to use.
-
-For more information, see
+field to use. For more information, see
 {xpack-ref}/ml-configuring-pop.html[Performing Population Analysis].
 
+[[detectors]]
+==== Detectors
+
+Each job must have one or more _detectors_. A detector applies an analytical 
+function to specific fields in your data. If your job does not contain a 
+detector or the detector does not contain a 
+{stack-ov}/ml-functions.html[valid function], you receive an error.
+
+If a job contains duplicate detectors, you also receive an error. Detectors are 
+duplicates if they have the same `function`, `field_name`, `by_field_name`, 
+`over_field_name` and `partition_field_name`. 
+
 [[influencers]]
 ==== Influencers
 
@@ -60,3 +74,50 @@ do not need more than three. If you pick many influencers, the results can be
 overwhelming and there is a small overhead to the analysis.
 
 The job creation wizards in {kib} can suggest which fields to use as influencers.
+
+[[model-memory-limits]]
+==== Model memory limits
+
+For each job, you can optionally specify a `model_memory_limit`, which is the 
+approximate maximum amount of memory resources that are required for analytical 
+processing. The default value is 1 GB. Once this limit is approached, data 
+pruning becomes more aggressive. Upon exceeding this limit, new entities are not 
+modeled. 
+
+You can also optionally specify the `xpack.ml.max_model_memory_limit` setting. 
+By default, it's not set, which means there is no upper bound on the acceptable 
+`model_memory_limit` values in your jobs. 
+
+TIP: If you set the `model_memory_limit` too high, it will be impossible to open 
+the job; jobs cannot be allocated to nodes that have insufficient memory to run 
+them.
+
+If the estimated model memory limit for a job is greater than the model memory 
+limit for the job or the maximum model memory limit for the cluster, the job 
+creation wizards in {kib} generate a warning. If the estimated memory 
+requirement is only a little higher than the `model_memory_limit`, the job will 
+probably produce useful results. Otherwise, the actions you take to address 
+these warnings vary depending on the resources available in your cluster:
+
+* If you are using the default value for the `model_memory_limit` and the {ml} 
+nodes in the cluster have lots of memory, the best course of action might be to 
+simply increase the job's `model_memory_limit`. Before doing this, however, 
+double-check that the chosen analysis makes sense. The default 
+`model_memory_limit` is relatively low to avoid accidentally creating a job that 
+uses a huge amount of memory.
+* If the {ml} nodes in the cluster do not have sufficient memory to accommodate 
+a job of the estimated size, the only options are:
+** Add bigger {ml} nodes to the cluster, or 
+** Accept that the job will hit its memory limit and will not necessarily find 
+all the anomalies it could otherwise find.
+
+If you are using {ece} or the hosted Elasticsearch Service on Elastic Cloud, 
+`xpack.ml.max_model_memory_limit` is set to prevent you from creating jobs 
+that cannot be allocated to any {ml} nodes in the cluster. If you find that you 
+cannot increase `model_memory_limit` for your {ml} jobs, the solution is to 
+increase the size of the {ml} nodes in your cluster.
+
+For more information about the `model_memory_limit` property and the 
+`xpack.ml.max_model_memory_limit` setting, see 
+{ref}/ml-job-resource.html#ml-analysisconfig[Analysis limits] and 
+{ref}/ml-settings.html[Machine learning settings].

docs/settings/apm-settings.asciidoc

@@ -13,3 +13,16 @@ You do not need to configure any settings to use APM. It is enabled by default.
 
 xpack.apm.enabled:: Set to `false` to disabled the APM plugin {kib}. Defaults to
 `true`.
+
+xpack.apm.ui.enabled:: Set to `false` to hide the APM plugin {kib} from the menu. Defaults to
+`true`.
+
+apm_oss.indexPattern:: Index pattern is used for integrations with Machine Learning and Kuery Bar. It must match all apm indices. Defaults to `apm-*`.
+
+apm_oss.errorIndices:: Matcher for indices containing error documents. Defaults to `apm-*-error-*`.
+
+apm_oss.onboardingIndices:: Matcher for indices containing onboarding documents. Defaults to `apm-*-onboarding-*`.
+
+apm_oss.spanIndices:: Matcher for indices containing span documents. Defaults to `apm-*-span-*`.
+
+apm_oss.transactionIndices:: Matcher for indices containing transaction documents. Defaults to `apm-*-transaction-*`.

package.json

@@ -77,7 +77,7 @@
     "url": "https://github.com/elastic/kibana.git"
   },
   "dependencies": {
-    "@elastic/eui": "3.0.0",
+    "@elastic/eui": "3.2.1",
     "@elastic/filesaver": "1.1.2",
     "@elastic/numeral": "2.3.2",
     "@elastic/ui-ace": "0.2.3",
@@ -128,8 +128,8 @@
     "fetch-mock": "^5.13.1",
     "file-loader": "1.1.4",
     "font-awesome": "4.4.0",
-    "glob": "5.0.13",
-    "glob-all": "3.0.1",
+    "glob": "^7.1.2",
+    "glob-all": "^3.1.0",
     "good-squeeze": "2.1.0",
     "h2o2": "5.1.1",
     "h2o2-latest": "npm:h2o2@8.1.2",
@@ -140,8 +140,6 @@
     "http-proxy-agent": "^2.1.0",
     "https-proxy-agent": "^2.2.1",
     "inert": "4.0.2",
-    "jade": "1.11.0",
-    "jade-loader": "0.8.0",
     "joi": "10.4.1",
     "jquery": "^3.3.1",
     "js-yaml": "3.4.1",
@@ -158,7 +156,7 @@
     "lodash": "3.10.1",
     "lru-cache": "4.1.1",
     "markdown-it": "^8.4.1",
-    "minimatch": "2.0.10",
+    "minimatch": "^3.0.4",
     "mkdirp": "0.5.1",
     "moment": "^2.20.1",
     "moment-timezone": "^0.5.14",
@@ -170,6 +168,7 @@
     "postcss-loader": "2.0.6",
     "prop-types": "15.5.8",
     "proxy-from-env": "1.0.0",
+    "pug": "^2.0.3",
     "querystring-browser": "1.0.4",
     "raw-loader": "0.5.1",
     "react": "^16.3.0",
@@ -239,6 +238,7 @@
     "@types/bluebird": "^3.1.1",
     "@types/chance": "^1.0.0",
     "@types/classnames": "^2.2.3",
+    "@types/enzyme": "^3.1.12",
     "@types/eslint": "^4.16.2",
     "@types/execa": "^0.9.0",
     "@types/fetch-mock": "^5.12.2",
@@ -294,7 +294,7 @@
     "getopts": "2.0.0",
     "globby": "^8.0.1",
     "grunt": "1.0.1",
-    "grunt-cli": "0.1.13",
+    "grunt-cli": "^1.2.0",
     "grunt-contrib-watch": "^1.0.0",
     "grunt-karma": "2.0.0",
     "grunt-peg": "^2.0.1",
@@ -328,11 +328,12 @@
     "mocha": "3.3.0",
     "mock-fs": "^4.4.2",
     "murmurhash3js": "3.0.1",
+    "mutation-observer": "^1.0.3",
     "ncp": "2.0.0",
     "nock": "8.0.0",
     "node-sass": "^4.9.0",
     "pixelmatch": "4.0.2",
-    "prettier": "^1.12.1",
+    "prettier": "^1.14.0",
     "proxyquire": "1.7.11",
     "simple-git": "1.37.0",
     "sinon": "^5.0.7",

packages/kbn-dev-utils/src/proc_runner/observe_readable.js

@@ -30,8 +30,14 @@ import { first, ignoreElements, map } from 'rxjs/operators';
  */
 export function observeReadable(readable) {
   return Rx.race(
-    Rx.fromEvent(readable, 'end').pipe(first(), ignoreElements()),
+    Rx.fromEvent(readable, 'end').pipe(
+      first(),
+      ignoreElements()
+    ),
 
-    Rx.fromEvent(readable, 'error').pipe(first(), map(err => Rx.throwError(err)))
+    Rx.fromEvent(readable, 'error').pipe(
+      first(),
+      map(err => Rx.throwError(err))
+    )
   );
 }

packages/kbn-es/src/install/archive.js

@@ -52,10 +52,14 @@ exports.installArchive = async function installArchive(archive, options = {}) {
   await decompress(archive, installPath);
   log.info('extracted to %s', chalk.bold(installPath));
 
+  if (license === 'trial') {
+    // starting in 6.3, security is disabled by default. Since we bootstrap
+    // the keystore, we can enable security ourselves.
+    await appendToConfig(installPath, 'xpack.security.enabled', 'true');
+  }
+
   if (license !== 'oss') {
     await appendToConfig(installPath, 'xpack.license.self_generated.type', license);
-
-    await appendToConfig(installPath, 'xpack.security.enabled', 'true');
     await configureKeystore(installPath, password, log);
   }
 

packages/kbn-es/src/utils/decompress.js

@@ -27,8 +27,7 @@ const tarFs = require('tar-fs');
 
 function decompressTarball(archive, dirPath) {
   return new Promise((resolve, reject) => {
-    fs
-      .createReadStream(archive)
+    fs.createReadStream(archive)
       .on('error', reject)
       .pipe(zlib.createGunzip())
       .on('error', reject)

packages/kbn-eslint-import-resolver-kibana/README.md

@@ -1,4 +1,4 @@
-# @elastic/eslint-import-resolver-kibana
+# @kbn/eslint-import-resolver-kibana
 
 Resolver for Kibana imports, meant to be used with [eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import).
 

packages/kbn-i18n/README.md

@@ -72,25 +72,21 @@ export default function (kibana) {
 }
 ```
 
-The engine uses a locale resolution process similar to that of the built-in
-Intl APIs to determine which locale data to use based on the `accept-language`
-http header.
-
-The following are the abstract steps i18n engine goes through to resolve the locale value:
-
-- If there's data for the specified locale (localization file is registered in
-  `uiExports.translations`), then that locale will be resolved.
-- If locale data is missing for a leaf locale like `fr-FR`, but there is data
-for one of its ancestors, `fr` in this case, then its ancestor will be used.
-- If `accept-language` header is not presented or previous steps didn't resolve
-the locale, the locale will be resolved to locale defined in `i18n.defaultLocale`
-option at `config/kibana.yml` file.
-
-One of our technical requirements is to have default message in the templates
-themselves, and that message will always be english, so we don't need interact
-with `en.json` file directly. We can generate that file from `defaultMessage`s
+The engine uses a `config/kibana.yml` file for locale resolution process. If locale is
+defined via `i18n.locale` option in `config/kibana.yml` then it will be used as a base
+locale, otherwise i18n engine will fall back to `en`. The `en` locale will also be used
+if translation can't be found for the base non-English locale.
+
+One of our technical requirements is to have default messages in the templates
+themselves, and those messages will always be in English, so we don't have to keep
+`en.json` file in repository. We can generate that file from `defaultMessage`s
 defined inline.
 
+__Note:__ locale defined in `i18n.locale` and the one used for translation files should
+match exactly, e.g. `i18n.locale: zn` and `.../translations/zh_CN.json` won't match and
+default English translations will be used, but `i18n.locale: zh_CN` and`.../translations/zh_CN.json`
+or `i18n.locale: zn` and `.../translations/zn.json` will work as expected.
+
 ## I18n engine
 
 I18n engine is the platform agnostic abstraction that helps to supply locale

packages/kbn-i18n/package.json

@@ -20,7 +20,6 @@
     "cross-env": "^5.2.0"
   },
   "dependencies": {
-    "accept-language-parser": "^1.5.0",
     "intl-format-cache": "^2.1.0",
     "intl-messageformat": "^2.2.0",
     "intl-relativeformat": "^2.1.0",