## Summary
Fixes the non-legacy ES test client to work with SSL.
Without this if you try to migrate `siem rules` or `alerting` or `CASE` or anything else that is using SSL based tests you get this error when trying to use the non-legacy:
```ts
// pull in non-legacy service for functional tests
const es = getService('es');
```
```ts
// use it somewhere where your config.ts is utilizing SSL in a functional test
// ...
```
In your console you get this error:
```ts
ConnectionError: self signed certificate in certificate chain
at onResponse (node_modules/@elastic/elasticsearch/lib/Transport.js:205:13)
at ClientRequest.request.on.err (node_modules/@elastic/elasticsearch/lib/Connection.js:98:9)
at TLSSocket.socketErrorListener (_http_client.js:401:9)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
```
This fixes that by adding the CA certs from test to the ES test client.
* reset settings when navigate to choose-settings-step page
* reset settings when navigate to choose-settings-step page
* reset settings when navigate to choose-settings-step page
* move core provier to NP. allows to run tests on every page
* remove no-base-path
* pass whole KbnTestServer config
* fix build path
* another id
* np
* build kibana tests plugins. it is used in xpack tests
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Extended alerting documentation with information about using Kibana keystore and action types for preconfigured connectors
* Fixed due to comments and merged two preconfig pages
* Fixed due to review comments
* Update docs/user/alerting/action-types/index.asciidoc
Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
* Fixed due to comments
* -
Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
## Summary
Fixes up the API contracts to work outside of a request and as a regular plugin.
* Removes space and request stuff that is not needed
* Adds in plugin ability with space id and user name being pushed down
* Changed assertion to loop through expected keys and confirm that they are contained within the array. Also made sure that the two arrays have the same length. Those two assertions should make sure that the contents are the same no matter the order of the keys.
* Changed assertion to loop through expected keys and confirm that they are contained within the array. Also made sure that the two arrays have the same length. Those two assertions should make sure that the contents are the same no matter the order of the keys.
* Fixed typo in function.
* Changed assertion per conversation.
* Updated assertion on second test.
* Fixed assertion for equality that's not strict.
* Added comment to code to explain why the arrays were sorted.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Adds unit tests to the schema for input/output validation
* Changes the mocks to use a `file_name.mock.ts` pattern
* Introduces io-ts partials _carefully_ where I get both the partials and the required undefined in the types
* Introduces an Identity type to remove weird intersection types and make plain types when using io-ts.
* I Introduces a RequiredKeepUndefined in order to work with partials and keep the undefined as required for when the type is used directly within the code. This makes it simpler to force new functions/methods to have to push down `undefined`
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
