Merge branch 'master' into nls/alerts-grid

.bazelignore

@@ -8,7 +8,10 @@
 .idea
 .teamcity
 .yarn-local-mirror
-/bazel
+bazel-bin
+bazel-kibana
+bazel-out
+bazel-testlogs
 build
 node_modules
 target

.bazelrc.common

@@ -18,17 +18,16 @@ build --disk_cache=~/.bazel-cache/disk-cache
 build --repository_cache=~/.bazel-cache/repository-cache
 
 # Bazel will create symlinks from the workspace directory to output artifacts.
-# Build results will be placed in a directory called "bazel/bin"
+# Build results will be placed in a directory called "bazel-bin"
 # This will still create a bazel-out symlink in
 # the project directory, which must be excluded from the
 # editor's search path.
-build --symlink_prefix=bazel/
 # To disable the symlinks altogether (including bazel-out) we can use
 # build --symlink_prefix=/
 # however this makes it harder to find outputs.
 
 # Prevents the creation of bazel-out dir
-build --experimental_no_product_name_out_symlink
+# build --experimental_no_product_name_out_symlink
 
 # Make direct file system calls to create symlink trees
 build --experimental_inprocess_symlink_creation
@@ -83,7 +82,7 @@ test:debug --test_output=streamed --test_strategy=exclusive --test_timeout=9999
 run:debug --define=VERBOSE_LOGS=1 -- --node_options=--inspect-brk
 # The following option will change the build output of certain rules such as terser and may not be desirable in all cases
 # It will also output both the repo cache and action cache to a folder inside the repo
-build:debug --compilation_mode=dbg --show_result=1 --disk_cache=bazel/disk-cache --repository_cache=bazel/repository-cache
+build:debug --compilation_mode=dbg --show_result=1
 
 # Turn off legacy external runfiles
 # This prevents accidentally depending on this feature, which Bazel will remove.

.ci/packer_cache.sh

@@ -2,8 +2,10 @@
 
 set -e
 
-# cache image used by kibana-load-testing project
-docker pull "maven:3.6.3-openjdk-8-slim"
+if [[ "$(which docker)" != "" && "$(command uname -m)" != "aarch64" ]]; then
+  # cache image used by kibana-load-testing project
+  docker pull "maven:3.6.3-openjdk-8-slim"
+fi
 
 ./.ci/packer_cache_for_branch.sh master
 ./.ci/packer_cache_for_branch.sh 7.x

.eslintignore

@@ -48,4 +48,4 @@ snapshots.js
 /packages/kbn-monaco/src/painless/antlr
 
 # Bazel
-/bazel
+/bazel-*

.github/CODEOWNERS

@@ -348,6 +348,7 @@
 
 # Security Solution sub teams
 /x-pack/plugins/case @elastic/security-threat-hunting
+/x-pack/plugins/timelines @elastic/security-threat-hunting
 /x-pack/test/case_api_integration @elastic/security-threat-hunting
 /x-pack/plugins/lists @elastic/security-detections-response
 

.github/ISSUE_TEMPLATE/v8_breaking_change.md

@@ -2,7 +2,7 @@
 name: 8.0 Breaking change
 about: Breaking changes from 7.x -> 8.0
 title: "[Breaking change]"
-labels: Team:Elasticsearch UI, Feature:Upgrade Assistant, Breaking Change
+labels: Feature:Upgrade Assistant, Breaking Change
 assignees: ''
 
 ---
@@ -12,8 +12,8 @@ assignees: ''
 ******* LABEL CHANGES NECESSARY ********
 ****************************************
  
-Please add a "NeededFor:${TeamName}" label to denote the team that is
-requesting the breaking change to be surfaced in the Upgrade Assistant.
+Please add a team label to denote the team that the
+breaking change is applicable to.
  
 -->
 
@@ -30,16 +30,14 @@ requesting the breaking change to be surfaced in the Upgrade Assistant.
 <!-- e.g. Based on telemetry data, roughly 75% of our users will need to make changes to x. -->
 <!-- e.g. A majority of users will need to make changes to x. -->
 
-**How can we programmatically determine whether the cluster is affected by this breaking change?**
+**Can the change be registered with the [Kibana deprecation service](https://github.com/elastic/kibana/blob/master/docs/development/core/server/kibana-plugin-core-server.deprecationsservicesetup.md)?**
 
-**What can users do to address the change manually?**
+<!-- The deprecation service is consumed by the Upgrade Assistant to surface Kibana deprecations.
+  It provides a way for Kibana deprecations to be resolved automatically via an API
+  or manually by providing step-by-step instructions for users to follow. -->
 
-<!-- If applicable, describe the manual migration steps and/or link to available docs. -->
-
-**How could we make migration easier with the Upgrade Assistant?**
-
-<!-- This can be as basic as notifying the user about the deprecation and linking to some
-  migration docs, or as advanced as a dedicated UI for fixing the problem. -->
+<!-- Each plugin owner is responsible for registering their deprecations via the service.
+  Please link to the issue/PR that will add this functionality. -->
 
 **Are there any edge cases?**
 

.github/relabel.yml

@@ -0,0 +1,3 @@
+issues:
+  - missingLabel: needs-team
+    regex: ^(\:ml)|(Team:.*)$

.gitignore

@@ -75,5 +75,6 @@ report.asciidoc
 .yarn-local-mirror
 
 # Bazel
-/bazel
-/.bazelrc.user
+bazel
+bazel-*
+.bazelrc.user

.stylelintignore

@@ -1,3 +1,4 @@
 x-pack/plugins/canvas/shareable_runtime/**/*.s+(a|c)ss
 build
 target
+bazel-*

BUILD.bazel

@@ -2,6 +2,7 @@
 # other packages builds and need to be included as inputs
 exports_files(
   [
+    "tsconfig.base.json",
     "tsconfig.json",
     "package.json"
   ],

docs/api/actions-and-connectors/legacy/create.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Create connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<create-connector-api>> instead.
+deprecated::[7.13.0,Use <<create-connector-api>> instead.]
 
 Creates a connector.
 

docs/api/actions-and-connectors/legacy/delete.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Delete connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<delete-connector-api>> instead.
+deprecated::[7.13.0,Use <<delete-connector-api>> instead.]
 
 Deletes a connector by ID.
 

docs/api/actions-and-connectors/legacy/execute.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Execute connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<execute-connector-api>> instead.
+deprecated::[7.13.0,Use <<execute-connector-api>> instead.]
 
 Executes a connector by ID.
 

docs/api/actions-and-connectors/legacy/get.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Get connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<get-connector-api>> instead.
+deprecated::[7.13.0,Use <<get-connector-api>> instead.]
 
 Retrieves a connector by ID.
 

docs/api/actions-and-connectors/legacy/get_all.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Get all connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<get-all-connectors-api>> instead.
+deprecated::[7.13.0,Use <<get-all-connectors-api>> instead.]
 
 Retrieves all connectors.
 

docs/api/actions-and-connectors/legacy/list.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy List all connector types</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<list-connector-types-api>> instead.
+deprecated::[7.13.0,Use <<list-connector-types-api>> instead.]
 
 Retrieves a list of all connector types.
 

docs/api/actions-and-connectors/legacy/update.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy Update connector</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<update-connector-api>> instead.
+deprecated::[7.13.0,Use <<update-connector-api>> instead.]
 
 Updates the attributes for an existing connector.
 

docs/api/alerting/legacy/create.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy create alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<create-rule-api>> instead.
+deprecated::[7.13.0,Use <<create-rule-api>> instead.]
 
 Create {kib} alerts.
 

docs/api/alerting/legacy/delete.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy delete alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<delete-rule-api>> instead.
+deprecated::[7.13.0,Use <<delete-rule-api>> instead.]
 
 Permanently remove an alert.
 

docs/api/alerting/legacy/disable.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy disable alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<disable-rule-api>> instead.
+deprecated::[7.13.0,Use <<disable-rule-api>> instead.]
 
 Disable an alert.
 

docs/api/alerting/legacy/enable.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy enable alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<enable-rule-api>> instead.
+deprecated::[7.13.0,Use <<enable-rule-api>> instead.]
 
 Enable an alert.
 

docs/api/alerting/legacy/find.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy find alerts</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<find-rules-api>> instead.
+deprecated::[7.13.0,Use <<find-rules-api>> instead.]
 
 Retrieve a paginated set of alerts based on condition.
 

docs/api/alerting/legacy/get.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy get alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<get-rule-api>> instead.
+deprecated::[7.13.0,Use <<get-rule-api>> instead.]
 
 Retrieve an alert by ID.
 

docs/api/alerting/legacy/health.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy get Alerting framework health</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<get-alerting-framework-health-api>> instead.
+deprecated::[7.13.0,Use <<get-alerting-framework-health-api>> instead.]
 
 Retrieve the health status of the Alerting framework.
 

docs/api/alerting/legacy/list.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy list all alert types</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<list-rule-types-api>> instead.
+deprecated::[7.13.0,Use <<list-rule-types-api>> instead.]
 
 Retrieve a list of all alert types.
 

docs/api/alerting/legacy/mute.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy mute alert instance</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<mute-alert-api>> instead.
+deprecated::[7.13.0,Use <<mute-alert-api>> instead.]
 
 Mute an alert instance.
 

docs/api/alerting/legacy/mute_all.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy mute all alert instances</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<mute-all-alerts-api>> instead.
+deprecated::[7.13.0,Use <<mute-all-alerts-api>> instead.]
 
 Mute all alert instances.
 

docs/api/alerting/legacy/unmute.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy unmute alert instance</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<unmute-alert-api>> instead.
+deprecated::[7.13.0,Use <<unmute-alert-api>> instead.]
 
 Unmute an alert instance.
 

docs/api/alerting/legacy/unmute_all.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy unmute all alert instances</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<unmute-all-alerts-api>> instead.
+deprecated::[7.13.0,Use <<unmute-all-alerts-api>> instead.]
 
 Unmute all alert instances.
 

docs/api/alerting/legacy/update.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Legacy update alert</titleabbrev>
 ++++
 
-WARNING: Deprecated in 7.13.0. Use <<update-rule-api>> instead.
+deprecated::[7.13.0,Use <<update-rule-api>> instead.]
 
 Update the attributes for an existing alert.
 

docs/developer/contributing/index.asciidoc

@@ -1,7 +1,7 @@
 [[contributing]]
 == Contributing
 
-Whether you want to fix a bug, implement a feature, or add some other improvements or apis, the following sections will 
+Whether you want to fix a bug, implement a feature, add an improvement, or add APIs, the following sections will 
 guide you on the process. After committing your code, check out the link:https://www.elastic.co/community/contributor[Elastic Contributor Program] where you can earn points and rewards for your contributions.
 
 Read <<development-getting-started>> to get your environment up and running, then read <<development-best-practices>>.
@@ -53,24 +53,27 @@ To use a single paragraph of text, enter a `Release note:` or `## Release note`
 
 When you create the Release Notes text, use the following best practices:
 
-* Use present tense. 
+* Use active voice. 
 * Use sentence case.
-* When you create a feature PR, start with `Adds`.
-* When you create an enhancement PR, start with `Improves`. 
-* When you create a bug fix PR, start with `Fixes`.
-* When you create a deprecation PR, start with `Deprecates`.
+* When you create a PR that adds a feature, start with `Adds`.
+* When you create a PR that improves an existing feature, start with `Improves`. 
+* When you create a PR that fixes existing functionality, start with `Fixes`.
+* When you create a PR that deprecates functionality, start with `Deprecates`.
 
 [discrete]
 ==== Add your labels
 
+To make sure that your PR is included in the Release Notes, add the right label.
+
 [arabic]
 . Label the PR with the targeted version (ex: `v7.3.0`).
 . Label the PR with the appropriate GitHub labels:
-  * For a new feature or functionality, use `release_note:enhancement`.
-  * For an external-facing fix, use `release_note:fix`. We do not include docs, build, and test fixes in the Release Notes, or unreleased issues that are only on `master`.
-  * For a deprecated feature, use `release_note:deprecation`.
-  * For a breaking change, use `release_note:breaking`.
-  * To **NOT** include your changes in the Release Notes, use `release_note:skip`.
+  * `release_note:feature` — New user-facing features, significant enhancements to features, and significant bug fixes (in rare cases).
+  * `release_note:enhancement` — Minor UI changes and enhancements.
+  * `release_note:fix` — Fixes for bugs that existed in the previous release. 
+  * `release_note:deprecation` — Deprecates functionality that existed in previous releases.
+  * `release_note:breaking` — Breaking changes that weren't present in previous releases.
+  * `release_note:skip` — Changes that should not appear in the Release Notes. For example, docs, build, and test fixes, or unreleased issues that are only in `master`.
 
 
 include::development-github.asciidoc[leveloffset=+1]

docs/developer/plugin-list.asciidoc

@@ -537,6 +537,10 @@ Documentation: https://www.elastic.co/guide/en/kibana/master/task-manager-produc
 |Gathers all usage collection, retrieving them from both: OSS and X-Pack plugins.
 
 
+|{kib-repo}blob/{branch}/x-pack/plugins/timelines/README.md[timelines]
+|Timelines is a plugin that provides a grid component with accompanying server side apis to help users identify events of interest and perform root cause analysis within Kibana.
+
+
 |{kib-repo}blob/{branch}/x-pack/plugins/transform/readme.md[transform]
 |This plugin provides access to the transforms features provided by Elastic.
 

docs/development/core/public/kibana-plugin-core-public.doclinksstart.links.md

@@ -144,6 +144,7 @@ readonly links: {
             putComponentTemplateMetadata: string;
             putSnapshotLifecyclePolicy: string;
             putWatch: string;
+            simulatePipeline: string;
             updateTransform: string;
         }>;
         readonly observability: Record<string, string>;