* Update the ems-client dependency
This PR adds the `appName` and `appVersion` parameters used by ems-client. The `appVersion` parameter replaces the now deprecated `kbnVersion` parameter in ems-client.
* Review feedback
* Fix borked merge
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* initial implementation of configurable test users
* user superuser by default to match master
* referenced the configs in reporting and api integration
* setting the minimum number of default roles
* looking for x-pack tests with users and roles
* add testUserService in dashboard mode tests
* running only ciGroup7
* uncommenting - addign visualization
* re-enabling all CI groups to run on CI
* reinstating Jenkinsfile
* disable Test user for OIDC config
* improved logging and added Roles for OSS tests to get better info on the runs.
* disable test_user for auth tests
* don't fetch enabledPlugins when testuser disabled
* fix es-lint
* running oss tests with x-pack enabled
* [revertme] build default dist for oss tests
* updating NOTICE.txt file as it complained in the kibana intake tests
* changed to pick OSS builds
* trying a license change to trial
* switch back to xpack builds
* created a new sample data role and used it in homepage tests
* revert test/scripts/jenkins_ci_group.sh
* only refresh browser and wait for chrome if we are already on Kibana page
* fix large_string test to use minimum set of roles and privileges
* fix for date nanos custom timestamp with a configured role
* changes to the files with addition of new roles for the test_user
* reverting to OSS changes and few additions to the time_zone test to run as a test_user
* changes to security
* changes to the x-pack test to use elastic superuser
* fix for chart_types test
* fixes to area chart , input control test
* fix for dashboard filtering test and a new config role
* changes to handle the x-pack tests
* additional role for date nanos mixed
* added the logstash role to the accessibility tests
* removed telemetry setting
* docs+few changes to the tests
* removed Page navigation
* removed pageNavigation which was unused
* test/accessibility/apps/management.ts
* update management.ts
* aria label, and other changes
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* accidentally checked in a piped file with results.
* reverted
* unloading of logstash data, fixing aria label
* aria-label
* added the required role
* fix for tsvb chart
* fix for sample data test reverted home_page pageobject file
* changes to sample data test and visualize index file to incorporate OSS changes
* changes to describe() and some more changes to incorporate in settings_page
* re-adding the after()
* removed unwanted roles
* replaced kibana_user with kibana_admin
* added the check of deprecated kibana_user
* testing with kibana_admin role
* fix for discover test
* incorporated the review comments
* incorporated the review comments
* incorporate review comments and added restoreDefaults()
* removed describe.only
* reverted the OSS logic change I had here- pulled into seperate PR
* incorporated the review comments
* incorporated review changes
* adding hidden=true to find hidden kibanaChrome
* change field.test.tsx to be same as that of master branch
Co-authored-by: spalger <spalger@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Move over to new plugin space, working implementation
* Fixing tests for report_listing snapshots
* WIP: Fixing react-component tests
* Fixing report_info_button tests
* Fixing download linksies
* WIP: Final working implementation
* Fixing attachAction API + API URLs
* Let the past die. Kill it if you have to. That’s the only way to become what you were meant to be.
* Fixing stream-client for new platform APIs
* Fixing types and tests
* Fix broken mock
* Adds back in warnings to report info button
* kibana.json line-breaks on required plugins
* Fixing broked snapshots
* Fix license checks in client-side components
* Adding back in warnings to report_listing component
* Fix danglig unused import
* Adds license checks for basic to our csv panel action
* Fixes issues from prior fork
* Move relative pathing to absolute
* Fix POST URL copying as we've moved from static methods
* Fix layoutId props
* Fixes types for layoutId
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
When the user apply a background color manually from the UI,
this commit adapt the current colors to have a better contrast with
the chosen background color irrespective of the used dark/light theme
* Move redirect_when_missing to kibana utils
* Replace redirectWhenMissing in dashboard
* Replace redirectWhenMissing in discover
* Remove redirect in monitoring
* Remove extra import
* Move invalid vistype check into editor.js
* Mock the history folder
* Fix redirect when missing index or saved object
* Move history to discover services
* Use redirect to listing page
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [ML] Fixes to error handling for analytics jobs and file data viz
* [ML] Fix failing tests and address comments from review
* [ML] Add key prop to error messages map
* [ML] Add errors.ts
The current index threshold alert uses a `size` limit on term aggregation, when used, but does not sort the buckets, so it's just using descending count on the grouped buckets as the sort to determine what to return.
The watcher API for the index threshold notes this as "top N of", implying a sort.
This PR applies sorting when the using `groupBy: top`, and the `aggType != count`. For count, ES is already sorting the way we want.
The sort is calculated as a separate agg beside the date_range aggregation, which is the same metrics agg specified in the query - `aggType(aggField)`. This field is then referenced in a new `order` property in the terms agg, using 'asc' sorting for `min`, and `desc` sorting for `avg`, `max`, and `sum`.
This doesn't change the shape of the output at all, just changes which term buckets will be returned, if there are more term buckets than requested with the `termSize` parameter.
* Added variables button for text fields in Pagerduty component. Fixed bugs mentioned in https://github.com/elastic/kibana/issues/60067
* Fixed due to comments
* fixed language check issue
* Fixed tests
* Fixed due to comments
* Memo'ize some layout and EPM header components
* Split EPM home page into two tabs
* Clean up dead files and import paths
* Add empty state
* Use react routing for rendering tab content
* Fix import paths (again)
* [Maps] move MapSavedObject type out of telemetry
* move SavedObject from server to core/types
* review feedback
* results from check_published_api_changes
* test to verify alerts page header says alerts
* updating test with pr feedback
* updating test with pr feedback and better verbiage
* updating test with pr feedback for better test titling
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Move validated range files to new NP location
* Update refs in code
* Clean up old validated range files
* Change relative paths to 'kibana-react'. Some clean up
* Change to relative paths
* Fix i18n errors
* i18n clean up. Export module explicitly
* Change files over to TS to prevent build issue where validated range was missing
* Clean up TS conversion
* More clean up. Extend EuiRangeProps
* Remove unneeded ts-ignore
* Review feedback and test fixes
* Change double to single quotes
* min and max aren't always passed, make optional
* Type updates
* Review feedback. Set state to empty on init and add ignore comment
* Review feedback
* Add back in last 2 ts-ignores. Build fails without focusable attribute on EuiDualRange & No good alternatives for spread syntax in TS components
* Rollback change to state init. Initializing state to null actually triggers a react browser warning and complicates using 'prevState' in getDerivedStateFromProps
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Refactors signal rule alert type into a smaller executor
## Summary
* Breaks out the schema into its own file and function
* Breaks out the action group into its own file and function
* Moves misc types being added to this into the `./types` file
* Breaks out all the writing of errors and success into their own functions
* Uses destructuring to pull data out of some of the data types
* Tweaks the gap detection to accept a date instead of moment to ease "ergonomics"
* Updates unit tests for the gap detection
### 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
