* Basic setup of error plugin.
* Removed not used `function` files at `error` expression.
* Moved related components from canvas.
* Changed imports of components.
* Fixed renderer and storybook.
* Fixed types errors.
* Added limits.
* Removed useless translations and fixed .i18nrc.json
* added `done` handler call.
* Added more fixes fo i18nc.
* Added docs.
* More fixes of i18nrc.
* Fixed async functions.
Written current code, based on https://github.com/storybookjs/storybook/issues/7745
* Fixed one test with Expression input.
After changing the way of rendering in stories, all elements are mounting and componentDidMount is involved. The previous snapshot was without
mounted `monaco` editor.
* Fixed storybook error.
* More fixes.
* removed unused translations.
* Removed handlers and changed the way of handling `resize` and calling `done`.
* Fixed i18n error.
* Fixed storybook.
* Replaced Popover with EuiPopover.
* Moved `Popover` back to `canvas`
* Removed `Popover` export from presentation_utils components.
* Moved error_component and debug_component from presentation_util to expression_error.
* Fixed translations and imports.
* Moved `debug renderer` to `expression_error` plugin.
* Fixed error.
* Fixed lazy exports.
* Fixed imports
* Fixed storybook snapshot.
* Removed `.i18nrc.json`.
* Fixed color of `error`.
* Exported concrete elements from popover.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
###Summary
This PR adds the subfeature UI for alerts to security solution. Note that the ability to customize subfeatures is still a gold feature. How will this map with existing users? The feature and subfeature are tied. So if a user was previously assinged All for security solution - they would get all for alerts, etc.
It still remains behind a feature flag, so to see the change you'll need to have the following in your kibana.dev.yml
xpack.securitySolution.enableExperimental: ['ruleRegistryEnabled']
xpack.ruleRegistry.write.enabled: true
* Bump EUI to v35.0.0, update euiContextMapping to match latest i18n tokens
* Updated i18n_service jest snapshot
* Added license override for EUI
* Attempting to clean up some forced dependency resolutions
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Reporting] Refactor types for API response data
* fix api test
* Update x-pack/plugins/reporting/common/types.ts
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
* more verbose comments
* set comments in interface type definition
* Update x-pack/plugins/reporting/common/types.ts
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
* more strict
* Update x-pack/plugins/reporting/public/management/report_info_button.tsx
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
* Update x-pack/plugins/reporting/public/management/report_info_button.tsx
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
* fix suggestion
* fix accidental declaration of interface methods as function properties
* fix info panel
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
* Fix route validation
This param is not always required. Was already fixed for org version but the personal dashboard came later and was not fixed.
Original fix for org:
30d8b1dfa8 (diff-07f094b2a4719e8511f003d8e278a77cd6b808d11b14d1c528705f9b259c328fR373)
* Fix route to account for private github route
Previously had the org route hard-coded
* Move the logic for parsing the query params to template
Because the useEffect call comes after the initial render, the chrome flashes. We originally got around this by hiding the chrome always because in non-github scenarios, this worked fine.
However, because the oauth plugin sends the state in the quert params and uses the same URL, we need to parse that to determine whether this is an org or accoutn route. We now do that logic in the template and set the chrome before calling the useEffect.
We still need to pass both the parsed params and the original quert string because the redirect passes that string to the next view.
## Summary
* Fixes flake where it looks like pre-built rules can take longer than 1 minute to load, so I increased that to 5 minutes
* There are problems with how the `cy.intercept` is not always working on CI we don't understand yet, so I am removing the failing call but keeping the rest of the test for the failure.
Backporting these two into `7.14` to add stability to `7.14` tests as well.
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
This package was migrated to bazel, but the legacy style script commands
still exist in `package.json`. This removes these scripts to avoid
incorrectly building the package.
* Fix .kbnPageTemplate__pageSideBar getting overriden by passed classes
- due to it existing in ...rest, and ...rest coming after pageSideBarProps
* Add test
* Fix `sideBarClasses`
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
* temp use unverified snapshot
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* Revert "skip failing es promotion suite (#104469)"
This reverts commit 87971e74e1.
* Revert "skip failing es promotion suite (#104467)"
This reverts commit c72ad3edcb.
* Revert "skip failing es promotion suite (#104466)"
This reverts commit a0b36c75f5.
* Revert "skip failing es promotion suite (#104413)"
This reverts commit 9773e3f678.
* Revert "skip failing es promotion suite (#104409)"
This reverts commit 79608dcc9e.
* Revert "skip failing es promotion suite (#104366)"
This reverts commit dfc5dbb31b.
* Revert "skip failing es promotion suite (#104365)"
This reverts commit 269577703a.
* Revert "skip failing es promotion suite (#104364)"
This reverts commit 16f69d24b6.
* Revert "skip failing es promotion suite (#104362)"
This reverts commit 2e492c2083.
* Revert another commit to promote ES snapshot
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [maps] show actionable message when term joins have no matches
* include message about showing first 10
* fix formatting
* review feedback
* review feedback
* move performInnerJoins into its own function
* lint
* unit test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Show multifields when parent is not indexed
* [Discover] Fix for multi-fields when parent is not indexed
* Readd package.json
* Applying Tims suggestion
* Add a unit test
* Updating unit test so that it tests the right thing
* added a retry for checking that we are on the dashboard landing page
* added .only and removed .skip
* remove .only
* revert this: added .only for flaky test runner
* Remove .only
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [APM] Updates the APM static index pattern regardless of fleet migration status (#105469)
* Fixed and added more unit tests
* ignores eslint error for property name in mock object
* [APM] Fixes support for APM index pattern with data streams (#94702)
* fix unit test
* - Revert "fix unit test"
- tests each component of index pattern title for index matches
This reverts commit a3a27df4b6.
* addes support for apm data streams (traces-apm*) to timelines
* [APM] Adds support for apm data streams (traces-apm*) to security solution (#94702)
* fix unit tests
* reverting prepackaged_rules changes to be bumped later
## Summary
Removes EQL timestamp workaround we introduced earlier when we found the bug https://github.com/elastic/kibana/pull/103771 now that it has been fixed with the fields API https://github.com/elastic/elasticsearch/issues/74582
* Fixes the EQL timestamp issue by removing the workaround
* Introduces EQL timestamps being formatted as ISO8601 like we do with KQL
* Adds e2e tests for the EQL timestamps
* Removes some boiler plating around our e2e tests by adding two utilities of `getEqlRuleForSignalTesting` and `getThresholdRuleForSignalTesting` and reducing those e2e code areas.
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
