* Fixed auto follow actions
* Created a provider for all follower index table actions to fix modal auto-closing
* Moved i18n texts into a const to avoid duplication
* Removed unnecessary imports and added index.js file for follower_index_actions_provider imports
* Fixed wrong imports deletion
* Fixed wrong imports deletion
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Add react-motion package
This is needed to animate the loading progress bar in the Enterprise Search schema views
* Add shared interface
* Migrate IndexingStatusContent component
This is a straight copy/paste with only linting changes and tests added
* Migrate IndexingStatusErrors component
This is a copy/paste with linting changes and tests added. Also changed out the Link component to our EuiLinkTo component for internal routing
* Migrate IndexingStatus component
This is a straight copy/paste with only linting changes and tests added
* Migrate IndexingStatusFetcher component
This is a copy/paste with some modifications. The http/axios code has been removed in favor of the HTTPLogic in Kibana.
This is a WIP that I am merging to master until I can get it working in the UI. Without either Schema component in the UIs for App Search or Workplace Search this is only a POC. Will not backport until this is verified working and have written tests.
* Add i18n
* Revert "Add react-motion package"
This reverts commit 92db929d2a.
* Remove motion dependency
* Update copy
Co-authored-by: Constance <constancecchen@users.noreply.github.com>
* Refactor per code review
- Remove stui classes
- Inline status
Co-authored-by: Constance <constancecchen@users.noreply.github.com>
Reapplies the #84123 PR:
This PR changes the default term from “Resolved” to “Recovered”, as it fits most use cases and we feel users are most likely to understand its meaning across domains.
Passing in an empty string '' to useResolver() would trigger a wild card search across all indices and fields, potentially causing a timeout and the page would fail to load. The following pages were affected: Single Metric Viewer, Data frame analytics models list, Data frame analytics jobs list, Data frame analytics exploration page, File Data Visualizer (Data visualizer - Import data from a log file). This PR fixes it by passing undefined instead of '' to useResolver to avoid calling _fields_for_wildcard with an empty pattern. Jest tests were added to cover the two parameter scenarios empty string/undefined.
The url templates provided for call of the API with space information was missing the /api/ section in it.
(cherry picked from commit 35f1cc16eaa29666d7212402f57ab17858ebc96d)
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This PR changes the behavior of severity and risk score overrides in two ways:
- adds support for arrays in the mapped event fields (so a rule can be triggered by an event where e.g. `event.custom_severity` has a value like `[45, 70, 90]`)
- makes the logic of overrides more flexible, resilient to the incoming values (filters out junk, extracts meaningful values, does its best to find a value that would fit the mapping)
This PR changes the default term from “Resolved” to “Recovered”, as it fits most use cases and we feel users are most likely to understand its meaning across domains.
* SavedObjectsRepository.incrementCounter supports array of fields
* Fix TS errors
* Fix failing test
* Ensure all the remarks make it into our documentation
* SavedObjectsRepository.incrementCounter initialize option
* Move usage collection-specific docs out of repository into usage collection plugins readme
* Update api docs
* Polish generated docs
* [Vega] Filtering is not working
Closes: #81738
* fix CI
* some work
* some work
* add tests for extract_index_pattern
* simplify extract_index_pattern
* fix type error
* cleanup
* Update vega_base_view.js
* Update extract_index_pattern.test.ts
* fix PR comments
* fix some comments
* findByTitle -> getByTitle
* remove getByTitle
* fix vega_base_view
* fix jest
* allow to set multiple indexes from top_nav
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* chore(NA): update gitignore to include first changes from moving into a single package.json
* chore(NA): update gitignore
* chore(NA): move all the dependencies into the single package.json and apply changes to bootstrap
* chore(NA): fix types problems after the single package json
* chore(NA): include code to find the dependencies used across the code
* chore(NA): introduce pure lockfile for install dependencies on build
* chore(NA): update clean task to not delete anything from xpack node_modules
* chore(NA): update gitignore to remove development temporary rules
* chore(NA): update notice file
* chore(NA): update jest snapshots
* chore(NA): fix whitelisted licenses to include a new specify form of an already included one
* chore(NA): remove check lockfile symlinks from child projects
* chore(NA): fix eslint and add missing declared deps on single pkg json
* chore(NA): correctly update notice
* chore(NA): fix failing jest test for storyshots.test.tsx
* chore(NA): fix cypress multi reporter path
* chore(NA): fix Project tests check
* chore(NA): fix problem with logic to detect used dependes on oss build
* chore(NA): include correct x-pack plugins dep discovery
* chore(NA): discover entries under dynamic requires on vis_type_timelion
* chore(NA): remove canvas
* chore(NA): add initial code to find circular deps
* chore(NA): ground work to integrate the circular deps scripts
* chore(NA): add correct filtering to find circular dependenices feature
* chore(NA): add ci mode flag into circular deps script
* chore(NA): feature complete circular dependencies detect script
* chore(NA): merge and solve conflicts with master
* chore(NA): remove unwanted changes
* chore(NA): remove unwanted changes on kbn storybook
* chore(NA): hook find circular deps tool into ci
* chore(NA): remove previous find plugin circular deps script
* chore(NA): add type for circular dep list
* chore(NA): add type for circular dep list for allowed list
* chore(NA): allow CI to fail check
* chore(NA): update deps allowed list
* chore(NA): run search circular deps script over examples too
* docs(NA): adds cli description
* chore(NA): use plugin search paths to build entries to find circular deps
* chore(NA): update allowed list
* chore(NA): snapshot update for kbn optimizer test
* chore(NA): update dpdm version
* chore(NA): remove thirdParty flag
* chore(NA): update docs to include info about the new tool
* docs(NA): update to link PR instead of the issue
* chore(NA): update debug logs to always output allowedList
* fix(NA): correctly list found differences number
* chore(NA): remove quiet flag
* fix(NA): correctly fail the CI if circular deps are found
* chore(NA): complete list of found circular deps
* chore(NA): used named capturing group into the regex
* docs(NA): update typescript best practices docs and styleguide
* chore(NA): introduce quick filter option flag
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Do not render out-of-box integration policy configuration step if a custom UI extension is registered
* Remove endpoint specific logic from fleet and move it to UI extension
* remove unused "paths" from tsconfig
* remove unused test utils, import get-url from kbn/test
* dont pollute globals with jest when importing getUrl
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [ML] store query string in the URL state
* [ML] query state for the config step
* [ML] pagination in the URL state
* [ML] persisted URL state for outlier results exploration
* [ML] update URL generator
* [ML] do not update the url state when query string hasn't been changed
* [ML] store expandable panels state in the URL
* [ML] fix TS issue
* [ML] fix TS issue
This PR addresses some weird UX we've identified with default values in Action Params components and their inferred defaults when placed inside of an Alerts flyout.
Key changes:
1. Typing of these components has been corrected to reflect that we expect these parameters to only be _partial_, as the form is used to set these values (for example, the `message` field of the Server Log action, might or might not be set, so it should be nullable, but in the typing we treated it as the _final_ valid state, which is message not being nullable).
2. When a default message is set by the params components, the are tracked against the value of the default, which means that if the default changes, then so will the value in the field. Custom values provided by the user will not be overridden when the default changes. This has to be handled by the component itself at the moment (hopefully in the future we can make this a concern of the flyout and not each component).
3. The concept of the "Recovered" action group has been removed from these components - that's an Alerting concern, not actions, and shouldn't appear in the action components' code.
* Update indexPatternSelect to get fields from indexPatternService instead of savedObject attributes
* keep original search implemenation
* import from public
* remove unused code
* API updates
* review feedback
