* [Maps] Map settings: min and max zoom
* eslint
* header and footer
* zoom range UI
* save session state in mapStateJSON
* disable button when flyout is open
* tslint
* update layer_control jest test
* tslint
* move settings button to top map chrome
* move map_settings_panel to NP
* remove merge conflict artifact
* fix import for NP migration
* remove unused CSS class
* fix path from NP move
* review feedback
* load map settings in embeddable
Starting Storybook (with `yarn storybook apm`) was failing to start because it was having trouble loading Angular .html templates.
Use the raw loader in the webpack config for storybook, same as the Webpack config in kbn-optimizer.
* install template after pipeline creation
* return installed pkg if this pkg version is already installed
* remove pipelines after templates are updated
* remove kibana saved objects assets before installing
* update current write indices
* add back removal of merging previous references lost in rebase
* improve some typing names, consolidate, fix bad merges
* update query to use aggregate on _index
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* WIP: Register saved objects types in NP
This works, but responsibilities are spread around. Refactor incoming.
* Moves new SO definitions into corresponding folders
This way our top-level file still acts as the index, but these are
more/less unconnected if/when we split these out into separate
applications.
* Replace raw SO updates with our ruleStatusSavedObjectsClient
This mainly consolidates the SO type name and the attributes type to a single
file so that we don't have to import both any time we want to work with
RuleStatus SavedObjects.
* new hook providing generic event handler for use with react router
* Refactor of Header Naviagtion to use useNavigateByRouterEventHandler
* Policy list refactor to use useNavigateByRouterEventHandler hook
* Policy list Policy name link to use useNavigateByRouterEventHandler hook
* Host list use of useNavigateByRouteEventHandler
* Remove unused file
This was moved to a constant in common/constants.
* Remove unused types
Omit is now part of Typescript, and Pick3 is unused.
* Define and export SIEM's plugin contracts
They're empty for now.
* Import config type from config file
Instead of our plugin index, which could only cause circular
dependencies.
* SiemClient API uses getter function instead of direct property access
* Add public mock for SiemClient
* Fix typo in extract-mitre-attacks script
We were backgrounding the process (&) instead of ANDing it with the
linting. Whoops!
* Remove missed instance of old siemClient API
I missed this one when grepping, but typescript and CI saved me.
* Use our client mock in our test suite
This was causing some test failures as I forgot to update the client mock
* Update script following updates to the output's usage
This was changed in https://github.com/elastic/kibana/pull/55883 but the
script was not updated accordingly.
This now requires us to define a schema for each setting, which is a
little redundant given that we also have to type the useUiSetting calls;
this might be an issue between kibana-react and new UiSettings changes.
* source new platform for reporting ui config
* fix test types
* fix type check
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
### Summary
Minor updates to the All Rules monitoring table. Includes front end and backend changes:
- Displays dashes in the monitoring table when no values are present
- Displays `lastLookBackDate` only if the rule indexes events into the signals index, otherwise `lastLookBackDate` is set to null
* convert eslint scripts into TS
* update settings for BWC
* add script updating styles to pretter v2
* use default prettier config
* run npx once, point to the correct head branch, do not add to git
* throw if run script not on a clear branch
* run in a batch, add logging
The needed change is to rely on history as source of truth for location instead of window.location.
btw, This makes possible to test state syncing utils integration using createMemoryHistory()
One issue was discovered after this change:
When switching from context to discover url was incorrect. history.location inside state syncing utils didn't get the last update. This happened, because history instance created in discover wasn't used in context app and when all listeners unsubscribed from it - it stopped receiving location updates. To fix this I just reused one history instance in discover, context and their kbnUrlTracker
Improves the messaging when the Pager Duty action has trouble parsing the timestamp field and adds trimming on the timestamp's field to make us more flexible in handling the parsing and hence more likely to be forgiving of the input by the user.
As the timestamp relies on context variables provided via mustcahe templates, we can't reliably validate this field at alert creation time.
We address by:
1. Trimming the edges, which is required when parsing a date, should help prevent accidental spaces from breaking the parsing.
2. Checking for a mustache template on the client side and if there are none - we validate for a valid timestamp when the action is created.
* Enable include/exclude in Terms agg for numeric fields
Closes#4576
* Added a new component that allows adding multiple values
* Added some validation to include/exclude fields
* Removed unnecessary comments and accepted API changes
* Fixed i18n ID issue
* Refactored some code and fixed discard button issue
* Added SimpleNumberList component and value parsing in include_exclude.tsx
* Fixed merge conflict
* Fixed merge conflict
* Refactored some code
* Got rid of lodash isArray, added Number.isFinite where needed and changed symbol of string join and array split
* Added some more test cases to cover migrate_include_exclude_format write method
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary
* Adds exact check to cause failures whenever a schema is using t.exact({}) and that schema has extra keys at any level of the schema hierarchy.
* Fixes the exact check to work with unknown in a safe way and only do recursive checks for keys only when the unknown is an Object.
* Changes the output to use a format error mechanism which pushes all the errors onto one line to be consistent with the response errors. We can change this as a team to whatever we want I just put it to a comma separator as that is what the responses type checks were using downstream.
* Moves the downstream code up higher to be used within SIEM for timeline and detection engine.
* Adds tests in TDD/red light/green light fashion where I fail the extra key checks first and then pass them second.
### 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
* Move actions over
* Move connected components over
* Move components over
* Move selectors over
* Move embeddables over. Set up legacy presence to keep legacy maps embeddables working
* Move angular and services over. Some additional top-level files
* Some file moves. Move styles over to NP
* Handle feature catalogue entry in NP. Add plugin deps to kibana.json
* Move vis registration to NP
* Clean up linting comments. Add linting comments to route controller. Move common to NP
* Add back in i18n context for embeddable
* Fix jest test paths. Fix TS lint errors
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Adds a new xpack.reporting.csv.escapeFormulaValues boolean to auto-escape potentially bad cells
* Treat csvs with formulas differently than those that aren't escaped
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* use fixed table layout
* added markup structure / css for overview page
* add flyout and links to other pages
* add "alpha" messaging at bottom of all pages
* attrs instead of defaultProps on styled components
* use FormattedMessage on alpha messaging component
* remove leftover code
* remove unused import
* [DOCS] Alerting PagerDuty benefits
* [DOCS] Fixes broken link
* [DOCS] Organization changes
* [DOCS] Changes to meet template and incorporate review comments
* [DOCS] Fixed formatting of bulleted list
* [DOCS] Incorporates review comments
* Update docs/user/alerting/action-types/pagerduty.asciidoc
Co-Authored-By: Mike Côté <mikecote@users.noreply.github.com>
* [DOCS] Fixes naming and other formatting issues
Co-authored-by: Mike Côté <mikecote@users.noreply.github.com>
