Merge branch 'main' of https://github.com/elastic/kibana into connect…

…ors/servicenow-docs

.buildkite/scripts/steps/checks.sh

@@ -5,7 +5,7 @@ set -euo pipefail
 export DISABLE_BOOTSTRAP_VALIDATION=false
 .buildkite/scripts/bootstrap.sh
 
-.buildkite/scripts/steps/checks/commit/commit.sh
+.buildkite/scripts/steps/checks/precommit_hook.sh
 .buildkite/scripts/steps/checks/bazel_packages.sh
 .buildkite/scripts/steps/checks/telemetry.sh
 .buildkite/scripts/steps/checks/ts_projects.sh

.buildkite/scripts/steps/checks/precommit_hook.sh

@@ -0,0 +1,26 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+
+source .buildkite/scripts/common/util.sh
+
+# Runs pre-commit hook script for the files touched in the last commit.
+# That way we can ensure a set of quick commit checks earlier as we removed
+# the pre-commit hook installation by default.
+# If files are more than 200 we will skip it and just use
+# the further ci steps that already check linting and file casing for the entire repo.
+echo --- Run Precommit Hook
+
+echo "!!!!!!!! ATTENTION !!!!!!!!
+That check is intended to provide earlier CI feedback after we remove the automatic install for the local pre-commit hook.
+If you want, you can still manually install the pre-commit hook locally by running 'node scripts/register_git_hook locally'
+!!!!!!!!!!!!!!!!!!!!!!!!!!!"
+
+node scripts/precommit_hook.js \
+  --ref HEAD~1..HEAD \
+  --max-files 200 \
+  --verbose \
+  --fix \
+  --no-stage # we have to disable staging or check_for_changed_files won't see the changes
+
+check_for_changed_files 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' true

.buildkite/scripts/steps/package_testing/test.sh

@@ -41,9 +41,11 @@ trap "echoKibanaLogs" EXIT
 
 vagrant provision "$TEST_PACKAGE"
 
-# export TEST_BROWSER_HEADLESS=1
-# export TEST_KIBANA_URL="http://elastic:changeme@$KIBANA_IP_ADDRESS:5601"
-# export TEST_ES_URL=http://elastic:changeme@192.168.56.1:9200
+export TEST_BROWSER_HEADLESS=1
+export TEST_KIBANA_URL="http://elastic:changeme@$KIBANA_IP_ADDRESS:5601"
+export TEST_ES_URL="http://elastic:changeme@192.168.56.1:9200"
 
-# cd x-pack
-# node scripts/functional_test_runner.js --include-tag=smoke
+cd x-pack
+
+echo "--- FTR - Reporting"
+node scripts/functional_test_runner.js --config test/functional/apps/visualize/config.ts --include-tag=smoke --quiet

docs/dev-tools/console/console.asciidoc

@@ -12,7 +12,7 @@ To get started, open the main menu, click *Dev Tools*, then click *Console*.
 [role="screenshot"]
 image::dev-tools/console/images/console.png["Console"]
 
-NOTE: You cannot to interact with the REST API of {kib} with the Console.
+NOTE: **Console** supports only Elasticsearch APIs. You are unable to interact with the {kib} APIs with **Console** and must use curl or another HTTP tool instead.
 
 [float]
 [[console-api]]
@@ -137,4 +137,4 @@ shortcuts, click *Help*.
 If you don’t want to use *Console*, you can disable it by setting `console.ui.enabled`
 to `false` in your `kibana.yml` configuration file. Changing this setting
 causes the server to regenerate assets on the next startup,
-which might cause a delay before pages start being served.
+which might cause a delay before pages start being served.