Merge branch 'master' of github.com:elastic/kibana into cases-rule-re…

…gistry

.backportrc.json

@@ -3,6 +3,7 @@
  "targetBranchChoices": [
  { "name": "master", "checked": true },
  { "name": "7.x", "checked": true },
+ "7.15",
  "7.14",
  "7.13",
  "7.12",
@@ -32,7 +33,7 @@
  "targetPRLabels": ["backport"],
  "branchLabelMapping": {
  "^v8.0.0$": "master",
- "^v7.15.0$": "7.x",
+ "^v7.16.0$": "7.x",
  "^v(\\d+).(\\d+).\\d+$": "$1.$2"
  },
  "autoMerge": true,

CONTRIBUTING.md

@@ -1,5 +1,5 @@
 # Contributing to Kibana
 
-We understand that you may not have days at a time to work on Kibana. We ask that you read our [developer guide](https://www.elastic.co/guide/en/kibana/master/development.html) carefully so that you spend less time, overall, struggling to push your PR through our code review processes.
+If you are an employee at Elastic, please check out our Developer Guide [here](https://docs.elastic.dev/kibana-dev-docs/welcome).
 
-Our developer guide is written in asciidoc and located under [./docs/developer](./docs/developer) if you want to make edits or access it in raw form.
+If you are an external developer, we have a legacy developer guide [here](https://www.elastic.co/guide/en/kibana/master/development.html), or you can view the raw docs from our new, internal Developer Guide [here](./dev_docs/getting_started/dev_welcome.mdx). Eventually, our internal Developer Guide will be opened for public consumption.

dev_docs/tutorials/kibana_page_template.mdx

@@ -126,7 +126,7 @@ This is a built-in configuration that displays a very specific UI and requires v
 
 The `noDataConfig` is of type [`NoDataPagProps`](https://github.com/elastic/kibana/blob/master/src/plugins/kibana_react/public/page_template/no_data_page/no_data_page.tsx):
 
-1. `solution: string`: Single name for the current solution, used to auto-generate the title, logo, description, and button label *(required)*
+1. `solution: string`: Single name for the current solution, used to auto-generate the title, logo, and description *(required)*
 2. `docsLink: string`: Required to set the docs link for the whole solution *(required)*
 3. `logo?: string`: Optionally replace the auto-generated logo
 4. `pageTitle?: string`: Optionally replace the auto-generated page title (h1)
@@ -136,7 +136,7 @@ The `noDataConfig` is of type [`NoDataPagProps`](https://github.com/elastic/kiba
 
 There are two main actions for adding data that we promote throughout Kibana, Elastic Agent and Beats. They are added to the cards that are displayed by using the keys `elasticAgent` and `beats` respectively. For consistent messaging, these two cards are pre-configured but require specific `href`s and/or `onClick` handlers for directing the user to the right location for that solution.
 
-It also accepts a `recommended` prop as a boolean to promote one or more of the cards through visuals added to the UI. It will also place the `recommended` ones first in the list. By default, the configuration will recommend `elasticAgent`. Optionally you can also replace the `button` label by passing a string, or the whole component by passing a `ReactNode`.
+It also accepts a `recommended` prop as a boolean to promote one or more of the cards through visuals added to the UI. It will also place the `recommended` ones first in the list. Optionally you can also replace the `button` label by passing a string, or the whole component by passing a `ReactNode`.
 
 
 ```tsx
@@ -145,18 +145,20 @@ const hasData = checkForData();
 
 // No data configuration
 const noDataConfig: KibanaPageTemplateProps['noDataConfig'] = {
- solution: 'Observability',
+ solution: 'Analytics',
+ logo: 'logoKibana',
  docsLink: '#',
  actions: {
- elasticAgent: {
+ beats: {
  href: '#',
  },
- beats: {
+ elasticAgent: {
  href: '#',
  },
  },
 };
 
+// Conditionally apply the configuration if there is no data
 <KibanaPageTemplate
  solutionNav={/* Solution navigation still show if it exists and use the right template type */}
  pageHeader={/* Page header will be ignored */}

docs/development/core/server/kibana-plugin-core-server.elasticsearchservicesetup.legacy.md

@@ -14,7 +14,5 @@
 ```typescript
 legacy: {
  readonly config$: Observable<ElasticsearchConfig>;
- readonly createClient: (type: string, clientConfig?: Partial<LegacyElasticsearchClientConfig>) => ILegacyCustomClusterClient;
- readonly client: ILegacyClusterClient;
  };
 ```

docs/development/core/server/kibana-plugin-core-server.elasticsearchservicesetup.md

@@ -15,5 +15,5 @@ export interface ElasticsearchServiceSetup
 
 | Property | Type | Description |
 | --- | --- | --- |
-| [legacy](./kibana-plugin-core-server.elasticsearchservicesetup.legacy.md) | <code>{</code><br/><code> readonly config$: Observable&lt;ElasticsearchConfig&gt;;</code><br/><code>  readonly createClient: (type: string, clientConfig?: Partial&lt;LegacyElasticsearchClientConfig&gt;) =&gt; ILegacyCustomClusterClient;</code><br/><code> readonly client: ILegacyClusterClient;</code><br/><code> }</code> | |
+| [legacy](./kibana-plugin-core-server.elasticsearchservicesetup.legacy.md) | <code>{</code><br/><code> readonly config$: Observable&lt;ElasticsearchConfig&gt;;</code><br/><code> }</code> | |
 

docs/development/core/server/kibana-plugin-core-server.elasticsearchservicestart.legacy.md

@@ -14,7 +14,5 @@
 ```typescript
 legacy: {
  readonly config$: Observable<ElasticsearchConfig>;
- readonly createClient: (type: string, clientConfig?: Partial<LegacyElasticsearchClientConfig>) => ILegacyCustomClusterClient;
- readonly client: ILegacyClusterClient;
  };
 ```

docs/development/core/server/kibana-plugin-core-server.elasticsearchservicestart.md

@@ -17,5 +17,5 @@ export interface ElasticsearchServiceStart
 | --- | --- | --- |
 | [client](./kibana-plugin-core-server.elasticsearchservicestart.client.md) | <code>IClusterClient</code> | A pre-configured [Elasticsearch client](./kibana-plugin-core-server.iclusterclient.md) |
 | [createClient](./kibana-plugin-core-server.elasticsearchservicestart.createclient.md) | <code>(type: string, clientConfig?: Partial&lt;ElasticsearchClientConfig&gt;) =&gt; ICustomClusterClient</code> | Create application specific Elasticsearch cluster API client with customized config. See [IClusterClient](./kibana-plugin-core-server.iclusterclient.md)<!-- -->. |
-| [legacy](./kibana-plugin-core-server.elasticsearchservicestart.legacy.md) | <code>{</code><br/><code> readonly config$: Observable&lt;ElasticsearchConfig&gt;;</code><br/><code>  readonly createClient: (type: string, clientConfig?: Partial&lt;LegacyElasticsearchClientConfig&gt;) =&gt; ILegacyCustomClusterClient;</code><br/><code> readonly client: ILegacyClusterClient;</code><br/><code> }</code> | |
+| [legacy](./kibana-plugin-core-server.elasticsearchservicestart.legacy.md) | <code>{</code><br/><code> readonly config$: Observable&lt;ElasticsearchConfig&gt;;</code><br/><code> }</code> | |