* [Maps] fix Kibana does not recognize a valid geo_shape index when attempting to create a Tracking Containment alert
* tslint
* instead of forcing refresh on getIdsAndTitles, update index pattern service to add saved object to cache when index pattern is created
* simplify title check
* revert unneeded changes
* tslint
* api doc updates
* fix functional test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Actions UI] Changed PagerDuty action form UI to fill payload fields according to the API docs for Resolve and Acknowledge events.
* fixed test
* fixed test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* - minor refactor of 'description' -> 'typeDescription' for
generic processor descriptions
- added initial pass of generated descriptions for all processors
* fix i18n
* added wrapping div and title to description and changed default description to appear as placeholder
* reworked the description width and overflow styling
* only show the text title on hover when we are not showing the text input
* fixed a number of minor issues with using values as though they are strings and doing better serialization
* slight optimisation to scss
* - implement copy feedback
- clean up a lot of uses of "target_field = field". it is better
to not show these
- made "replacement" a required field on gsub (which it was not)
* revert the previouis validation as empty values are acceptbale for the replacement text
* - updated the copy per feedback and fixed a missing i18n.translate
- slight update to SCSS classes to not have unused class
* Added an empty string field validator that accepts spaces so that
the KV processor value and field split fields accept " "
* replace use of HTML "title" with EuiToolTip
* remove unused variable and import
* implemented feedback; removed if from default descriptions and other minor updates
* update default description of foreach to always display
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## [Security Solution] Fixes the `Read Less` button rendering below the fold
Fixes issue <https://github.com/elastic/kibana/issues/95295> where the `Read Less` button in the Event Details flyout is rendered below the fold when an event's `message` field is too large, per the `Before` and `After` screenshots below:
### Before
_Before: The `Read Less` button is not visible in the `Event details` flyout above_
### After
_After: The `Read Less` button is visible in the `Event details` flyout above_
In the _After_ screenshot above, the long `message` is rendered in a vertically scrollable view that occupies ~ one third of the vertical height of the viewport. The `Read Less` button is visible below the message.
### Desk Testing
Desk tested on a 16" MBP, and at larger desktop resolutions in:
- Chrome `89.0.4389.114`
- Firefox `87.0`
- Safari `14.0.3`
* change composite.size of snapshot query to improve speed
* use value from kibana config to set compositeSize, clean up unused config properties
* fix test
* change config name
* fix reference
Data Frame Analytics does not support cross-cluster search. This PR fixes the SourceSelection component to not allow a user to select a CCS index pattern or a saved search using a CCS index pattern.
* document SO batchsize and migrationsv2 enablement options
* use refs by name
* Update docs/setup/settings.asciidoc
Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
* apply Lukes suggestion
* add a note that migrations.enableV2 will be removed soon
* document migrations.retryAttempts
* Apply suggestions from code review
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
* Use correct prop name for disabling timeline context menu button
* Update usages of disabled to isDisabled on EuiIconButton
* Update failing snapshot and tests looking for old prop
* Add possibility to open visualization when saved field doesn't exists anymore
* Fix tests
* Fix some remarks
* Remove unneeded code
* Fix tests
* Fix tests
* Fix some remarks
* Fixed problem with double error popover in visualizations
* Fix CI
* Fix type
* Fix API docs
* Don't show error popup for error related to runtime fields
* Fix some remarks
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Implemented in-form Cloud deployment url input
* Fixed i18n files and added mode switch back for non-Cloud
* Added cloud docs link to the documentation service, fixed snapshot tests
* Fixed docs build
* Added jest test for the new cloud url input
* Added unit test for cloud validation
* Fixed eslint error
* Fixed ts errors
* Added ts-ignore
* Fixed ts errors
* Refactored connection mode component and component tests
* Fixed import
* Fixed copy
* Fixed copy
* Reverted docs changes
* Reverted docs changes
* Replaced the screenshot with a popover and refactored integration tests
* Added todo for cloud deployments link
* Changed cloud URL help text copy
* Added cloud base url and deleted unnecessary base path
* Fixed es error
* Fixed es error
* Changed wording
* Reverted docs changes
* Updated the help popover
* Deleted unneeded fragment component
* Deleted unneeded fragment component
* Updated tests descriptions to be more detailed
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
related to https://github.com/elastic/detection-rules/pull/1082
## Summary
Endgame promotion rules in Kibana/7.12 are at version 5 and have timestamp_override defined (which should not be). These same rules are at version 4 in the detection-rules repo 7.12 branch and kibana/master and timestamp_override is not defined. These updates are targeted for 7.12.1
There most likely was an issue with the maze of backports and interlaced updates.
To fix the rules, they need to be reconciled across:
detection-rules 7.12 & main
kibana 7.12.1 and master
bump detection-rules/7.12 to v6 -> PR to kibana/master -> backport to 7.12.1
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md)
### For maintainers
- [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
* [Fleet] Install security_rule assets as saved objects
* Add security-rule to update_assets.ts
* Update UUIDs for security_rule asset
* Change .type to match the saved object type not the asset type
* Add saved object mapping for security-rule
* Make SO non-hidden
* Fix SO mapping for security-rule
* Make security-rule a non-hidden asset
## Summary
As identified in https://github.com/elastic/kibana/pull/96505#issuecomment-815392671, this fixes the flakiness in the `Closing alerts` cypress test. Method used was to just delete the rule after the initial batch of alerts were generated. Alternatively we could add a function for disabling the rule (didn't see one in there), but the outcome is the same, no more alerts generated while the test is being performed. 🙂
> Passing locally, though upon further inspection, this test is definitely going to be flakey as it's checking counts on alerts as they move through different states and there are new alerts that keep coming in (hence the count mis-match in the above failure). Potential fixes would be to use an absolute daterange to after the first round of alerts were generated, or just stop generating alerts before performing the alert state changes.
##### Before:
<p align="center">
<img width="500" src="https://user-images.githubusercontent.com/2946766/113952824-ae1d9500-97d3-11eb-9021-6737544b9c50.png" />
</p>
##### After:
<p align="center">
<img width="500" src="https://user-images.githubusercontent.com/2946766/113958216-ed50e380-97dd-11eb-9d22-d1c6aafc97d2.png" />
</p>
