* [ML] api integration tests for get trained models endpoint
* [ML] delete ingest pipelines after tests execution
* [ML] deleteIngestPipeline method
* [ML] test for unauthorized user
* [ML] tests for model stats
* [ML] delete trained model tests
* [ML] fix typo
* [ML] fix expect package path
* [ML] get model pipelines tests
* [ML] test for aliases
* [ML] add tests for a 404 response
* [ML] fix typo
* [ML] fix typo
* use date range in search query
fixes elastic/security-team/issues/1137
* make any date selection fetch matching log
fixes elastic/security-team/issues/1137
* use a single action for updating paging info and fetching data
fixes elastic/security-team/issues/1137
* use consistent types
for some reason TS was complaining earlier with `undefined`
* reset date picker on tab load
fixes elastic/security-team/issues/1137
* refactor date pickers into a component
refs elastic/security-team/issues/1137
* clear dates on change of endpoint
fixes elastic/security-team/issues/1137
* do not show empty state if date filtering results return empty data
fixes elastic/security-team/issues/1137
* add tests
fixes elastic/security-team/issues/1137
* review changes
* update comment
refs f551b67d66
* store invalidDateRange on redux store and decouple logic from the component
review changes
* fix test
* fix lint
* review changes
* expand date picker to use the full width of the flyout
review changes
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Fix unsavedChanges false positive when MultiInputRows is present
- The fix for this is to change MultiInputRows from useEffect to useUpdateEffect, which prevents onChange from firing on initial mount/render (triggering updateBoostValue->unsavedChanges)
@see https://github.com/streamich/react-use/blob/master/docs/useUpdateEffect.md
* Fix precision tuner not triggering unsavedChanges
* Fixed `i18nrc not found ja-JP.json file` at expression_reveal_image.
* Fixed `i18nrc not found ja-JP.json file` at `screenshotMode`.
* Fixed `i18nrc not found ja-JP.json file` at `x-pack/plugins/timelines`.
Add an `EuiThemeProviderDecorator` to kibanaReact which uses the Storybook globals to set the EUI theme.
Add global decorators to the APM and Observability plugins so all stories are wrapped in the `EuiThemeProviderDecorator`, and they don't need to specify it in the stories.
Add [jest setup helpers recommended by @storybook/testing-react](https://github.com/storybookjs/testing-react#global-config).
* makeAllReportingPoliciesUnmanaged -> makeAllReportingIndicesUnmanaged
* expose the reporting services on the functional services object shared with a11y
* added data-test-subjs for a11y test
* added reporting a11y test
* updated jest test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Enrich events with ES data before rendering event filters modal
* Add unmounted component control check
* Fix error when closing and opening modal/flyout twice
* refactor: move `UserPrivilegesContext` to `public/common`
* Add endpointPrivileges to the UserPrivileges context
* refactor `useUpgradeSecurityPackages` to use `useUserPrivileges()`
* Refactor to use `useUserPrivileges()` instead of `useIngestEnabledCheck()`
* Refactor Overview page to use `useUserPrivileges()` instead of `useIngestEnabledCheck()`
* Delete `ingest_enabled` hook and refactor tests
An MVP of the RBAC work required for the "alerts as data" effort. An example of the existing implementation for alerts would be that of the security solution. The security solution stores its alerts generated from rules in a single data index - .siem-signals. In order to gain or restrict access to alerts, users do so by following the Elasticsearch privilege architecture. A user would need to go into the Kibana role access UI and give explicit read/write/manage permissions for the index itself.
Kibana as a whole is moving away from this model and instead having all user interactions run through the Kibana privilege model. When solutions use saved objects, this authentication layer is abstracted away for them. Because we have chosen to use data indices for alerts, we cannot rely on this abstracted out layer that saved objects provide - we need to provide our own RBAC! Instead of giving users explicit permission to an alerts index, users are instead given access to features. They don't need to know anything about indices, that work we do under the covers now.
Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
Co-authored-by: Yara Tercero <yara.tercero@elastic.co>
* Fix "Max size" number inputs cutting off the "No limit" placeholder text on Chrome/webkit
- textOnly={false} is required for the input to expand in width
* Fix handleFieldNumberBlur behavior:
- should allow setting a number field back to empty/no limits
- dev note: '' is the blank/empty state, which gets parsed to NaN. Random invalid strings ALSO get parsed to '', which is NaN
* Fix input not clearing invalid non-number strings
For some really odd reason, '' and undefined aren't correctly resetting the input value when a string gets entered into the input. I had to add a space for EUI to actually start clearing it
Note that this change completely prevents users from writing non-numbers into the input at all, but this is probably fine/valid honestly
