mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
3136 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
|
b5e1ef0740
|
replace kbn/ecs with official npm package holding ecs schema (#176128)
## Summary This PR replaces kbn/ecs package with the official ecs typescript defs available on npm https://www.npmjs.com/package/@elastic/ecs The idea here is to be able to update and maintain ecs type defs independently, and in a transparent way. ECS version used in kibana currently is 8.10.0, and after this PR is merged I will generate current version typings & file another PR to update the kibana dependency, The `alpha` suffix will be removed once this new flow of ecs management stabilizes. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
98536eba48
|
[Dataset quality] Implement Summary Panel (#175994)
closes https://github.com/elastic/kibana/issues/170247 ## 📝 Summary This PR introduces a new state machine for controlling the new Dataset Quality Summary Panel. As part of this work, we had to introduce a new endpoint to fetch and calculate the Estimated Data in last 24h. ## 💡For Reviewers ### State Machine The new state machine introduces 3 parallel states to fetch the values displayed in the summary panel. In case of failures in any of them, a retry mechanism is introduced to try the fetch 1 more time after 5 seconds interval. If the fetch fails again, we display an error toast notification.  (#176527)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@elastic/charts](https://togithub.com/elastic/elastic-charts) | [`63.0.0` -> `63.1.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/63.0.0/63.1.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>elastic/elastic-charts (@​elastic/charts)</summary> ### [`v63.1.0`](https://togithub.com/elastic/elastic-charts/blob/HEAD/CHANGELOG.md#6310-2024-01-29) [Compare Source](https://togithub.com/elastic/elastic-charts/compare/v63.0.0...v63.1.0) ##### Bug Fixes - **deps:** update dependency [@​elastic/eui](https://togithub.com/elastic/eui) to ^92.1.1 ([#​2315](https://togithub.com/elastic/elastic-charts/issues/2315)) ([f4e4fae]( |
||
|
f69c7496c4
|
chore: bump socks transitive dependency from 2.7.1 to 2.7.3 (#176693)
## Summary Bump `socks` transitive dependency from `2.7.1` to `2.7.3` to reduce a number of packages that depend on outdated `ip` package. |
||
|
8fb4bf2432
|
chore(NA): replace deprecated cuid with @paralleldrive/cuid2 (#174787)
## Summary `cuid` has been deprecated due to security concerns. This PR replaces `cuid` with the successor `@paralleldrive/cuid2` while keeping the usage intact. ### Checklist N/A ### Risk Matrix N/A ### 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) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
2627f48d95
|
Harden console functions (#171367)
## Summary This PR overrides console functions only in production, in order to sanitize input parameters for any potential calls made to the global console from Kibana's dependencies. This initial implementation overrides the `debug`, `error`, `info`, `log`, `trace`, and `warn` functions, and only sanitizes string inputs. Future updates may expand this to handle other types, or strings nested in objects. The unmodified console methods are now exposed internally in Kibana as `unsafeConsole`. Where needed for formatting (log appenders, core logger), calls to the global console have been replaced by `unsafeConsole`. This PR also adds a new es linting rule to disallow calls to `unsafeConsole` unless `eslint-disable-next-line @kbn/eslint/no_unsafe_console` is used. ### Testing Not sure how we could test this. The overrides are only enabled when running in a true production environment (e.g. docker) by checking `process.env.NODE_ENV`. I was able to manually test by adding additional console output denoting when the console functions were being overriden or not. Closes https://github.com/elastic/kibana-team/issues/664 Closes #176340 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
44df1f4caa
|
[Obs AI Assistant] Bedrock/Claude support (#176191)
~This PR still needs work (tests, mainly), so keeping it in draft for now, but feel free to take it for a spin.~ Implements Bedrock support, specifically for the Claude models. Architecturally, this introduces LLM adapters: one for OpenAI (which is what we already have), and one for Bedrock/Claude. The Bedrock/Claude adapter does the following things: - parses data from a SerDe (an AWS concept IIUC) stream using `@smithy/eventstream-serde-node`. - Converts function requests and results into XML and back (to some extent) - some slight changes to existing functionality to achieve _some_ kind of baseline performance with Bedrock + Claude. Generally, GPT seems better at implicit tasks. Claude needs explicit tasks, otherwise it will take things too literally. For instance, I had to use a function for generating a title because Claude was too eager to add explanations. For the `classify_esql` function, I had to add extra instructions to stop it from requesting information that is not there. It is prone to generating invalid XML. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
cb5cf0ebc9
|
Upgrade EUI to v93.0.0 (#176246)
`v92.2.1` ⏩ `v93.0.0` --- ## [`v93.0.0`](https://github.com/elastic/eui/releases/v93.0.0) **Bug fixes** - Fixed `EuiTextTruncate` component to clean up timer from side effect on unmount ([#7495](https://github.com/elastic/eui/pull/7495)) **Breaking changes** - Removed deprecated `anchorClassName` prop from `EuiPopover`. Use `className` instead ([#7488](https://github.com/elastic/eui/pull/7488)) - Removed deprecated `buttonRef` prop from `EuiPopover`. Use `popoverRef` instead ([#7488](https://github.com/elastic/eui/pull/7488)) - Removed deprecated `toolTipTitle` and `toolTipPosition` props from `EuiContextMenuItem`. Use `toolTipProps.title` and `toolTipProps.position` instead ([#7489](https://github.com/elastic/eui/pull/7489)) - Removed deprecated internal `setSelection` ref method from `EuiInMemoryTable` and `EuiBasicTable`. Use the new controlled `selection.selected` prop API instead. ([#7491](https://github.com/elastic/eui/pull/7491)) - `EuiTourStep`'s `className` and `style` props now apply to the anchoring element instead of to the popover panel, to match `EuiPopover` behavior. ([#7497](https://github.com/elastic/eui/pull/7497)) - Convert your existing usages to `panelClassName` and `panelStyle` respectively instead. **Performance** - Improved the amount of recomputed styles being generated by `EuiCode` and `EuiCodeBlock` ([#7486](https://github.com/elastic/eui/pull/7486)) **CSS-in-JS conversions** - Converted `EuiSearchBar` to Emotion ([#7490](https://github.com/elastic/eui/pull/7490)) - Converted `EuiEmptyPrompt` to Emotion ([#7494](https://github.com/elastic/eui/pull/7494)) - Added `euiBorderColor` and `useEuiBorderColorCSS` style utilities ([#7494](https://github.com/elastic/eui/pull/7494)) --------- Co-authored-by: Jon <jon@elastic.co> |
||
|
086c4690a5
|
Update dependency @elastic/charts to v63 (main) (#175316)
## Note about `@elastic/charts` BREAKING CHANGE In version 62.0.0 we introduced a breaking change in time-series charts: the default "extra" legend value now represents the last data point in the passed data array. It doesn't try to reconcile anymore the data computed domain with a passed domain in `Settings.xDomain` but instead it renders directly the last element of the passed array. The reasons for this change can be found at https://github.com/elastic/elastic-charts/pull/2115 or can be asked directly to our `#charts` slack channel There are a couple of implementations in Kibana that use both the `showLegendExtra` in the chart configuration. I've commented them out so that the owner teams can help me fix this breaking change if necessary. In general, the fix requires that the data passed to the chart contains all the buckets, even empty buckets with null/zeros should be passed. To achieve this, your ES query you should provide the `extended_bounds` settings in the [data histogram agg](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-histogram-aggregation.html#search-aggregations-bucket-histogram-aggregation-extended-bounds) and use a `min_doc_count:0`. If that doesn't work, please ping me and we can find an alternative solution. This should not limit the query performance, generating empty date buckets on the server side has a similar or even less performance impact than what we were doing on the client side to calculate every missing bucket, to fillup the chart in particular situations. Please double-check your queries/data fetches and push a commit to this PR or ping me with the updated data fetch strategy. fix https://github.com/elastic/kibana/issues/153079 This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@elastic/charts](https://togithub.com/elastic/elastic-charts) | [`61.2.0` -> `63.0.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/61.2.0/63.0.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>elastic/elastic-charts (@​elastic/charts)</summary> ### [`v63.0.0`](https://togithub.com/elastic/elastic-charts/blob/HEAD/CHANGELOG.md#6300-2024-01-24) [Compare Source](https://togithub.com/elastic/elastic-charts/compare/v62.0.0...v63.0.0) ##### Features - **legend:** expose extra raw values ([#​2308](https://togithub.com/elastic/elastic-charts/issues/2308)) ([85bfe06]( |
||
|
6f340bccc1
|
[data views / ES|QL] Set type on esql related data views (#172622)
## Summary Identify ES|QL data views as such by setting type attribute. Also creates `data-view-utils` package so dependency annoyances can be avoided by consumers. Part of https://github.com/elastic/kibana/issues/168131 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
86e8bc197b
|
[CodeEditor/UrlDrilldown] Add fitToContent support, autoresize the url template editor (#175561)
## Summary This PR fixes the paper cut where the URL template editor in URL drilldown is unusably small. It now can expand as you type longer URLs fix https://github.com/elastic/kibana/issues/132513 The input box now expands from 5 to 15 lines. |
||
|
9f1f142986
|
Detect rule param changes for rolling upgrades and rollback assessment (#173936)
In this PR, I'm adding a test in the alerting framework to detect changes in a rule type's params schema that will require a snapshot to be updated. This snapshot will provide a centralized place to view history on alerting rule params in case we need to asses risk for rolling upgrades or rollbacks of a release (serverless). The only rule types affected are those running in serverless in any of the three project types. When a rule type is used in serverless, it must provide one of the following configuration to their rule type on top of everything else: ``` // Zod schema schemas: { params: { type: 'zod', schema: UnifiedQueryRuleParams }, }, // config-schema schemas: { params: { type: 'config-schema', schema: EsQueryRuleParamsSchema, }, }, ``` We are working on documenting guidelines so engineers and response ops can ensure a change to rule parameters will work properly in rolling upgrade and rollback scenarios and be part of the PR review process. NOTE to rule type owners: I pass the same schema used to validate to the `schemas.params` attribute in the rule type. It will be important to keep them in sync. Down the road, we plan to make `validate.params` optional and use the schema as a starting point so it's easier to have a single variable passed in. ## To verify 1. Make changes to the params schema of the ES query rule type. ``` diff --git a/x-pack/plugins/stack_alerts/server/rule_types/es_query/rule_type_params.ts b/x-pack/plugins/stack_alerts/server/rule_types/es_query/rule_type_params.ts index 73e8eae32cf..09ec74104ec 100644 --- a/x-pack/plugins/stack_alerts/server/rule_types/es_query/rule_type_params.ts +++ b/x-pack/plugins/stack_alerts/server/rule_types/es_query/rule_type_params.ts @@ -39,6 +39,7 @@ export type EsQueryRuleParamsExtractedParams = Omit<EsQueryRuleParams, 'searchCo }; const EsQueryRuleParamsSchemaProperties = { + foo: schema.boolean(), size: schema.number({ min: 0, max: ES_QUERY_MAX_HITS_PER_EXECUTION }), timeWindowSize: schema.number({ min: 1 }), excludeHitsFromPreviousRun: schema.boolean({ defaultValue: true }), ``` 2. Run the jest integration test to update the snapshot file ``` node scripts/jest_integration.js x-pack/plugins/alerting/server/integration_tests/serverless_upgrade_and_rollback_checks.test.ts -u ``` 3. Notice the `x-pack/plugins/alerting/server/integration_tests/__snapshots__/serverless_upgrade_and_rollback_checks.test.ts.snap` file got updated ``` "foo": Object { "flags": Object { "error": [Function], }, "type": "boolean", }, ``` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
ff3c1af8ee
|
[chore] update chromedriver to 121 (#176190)
Bumping chromedriver to the latest version |
||
|
81ccdc2ac5
|
[Security Solution] Remove kbn-url-state package (#176122)
## Summary This PR removes unused kbn url state package. It was only used in the flyout and is now replaced with a shared utility, used by several other modules. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
8d2feeabbc
|
Update cypress (main) (#173228)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@cypress/code-coverage](https://togithub.com/cypress-io/code-coverage) | [`^3.10.0` -> `^3.12.18`](https://renovatebot.com/diffs/npm/@cypress%2fcode-coverage/3.10.0/3.12.18) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [@cypress/grep](https://togithub.com/cypress-io/cypress/tree/develop/npm/grep#readme) ([source](https://togithub.com/cypress-io/cypress)) | [`^3.1.5` -> `^4.0.1`](https://renovatebot.com/diffs/npm/@cypress%2fgrep/3.1.5/4.0.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [@cypress/webpack-preprocessor](https://togithub.com/cypress-io/cypress/tree/develop/npm/webpack-preprocessor#readme) ([source](https://togithub.com/cypress-io/cypress)) | [`^5.12.2` -> `^6.0.1`](https://renovatebot.com/diffs/npm/@cypress%2fwebpack-preprocessor/5.12.2/6.0.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [cypress](https://cypress.io) ([source](https://togithub.com/cypress-io/cypress)) | [`^13.3.0` -> `^13.6.3`](https://renovatebot.com/diffs/npm/cypress/13.3.0/13.6.3) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [cypress-data-session](https://togithub.com/bahmutov/cypress-data-session) | [`^2.7.0` -> `^2.8.0`](https://renovatebot.com/diffs/npm/cypress-data-session/2.7.0/2.8.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [cypress-multi-reporters](https://togithub.com/you54f/cypress-multi-reporters) | [`^1.6.3` -> `^1.6.4`](https://renovatebot.com/diffs/npm/cypress-multi-reporters/1.6.3/1.6.4) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [cypress-real-events](https://togithub.com/dmtrKovalenko/cypress-real-events) | [`^1.10.3` -> `^1.11.0`](https://renovatebot.com/diffs/npm/cypress-real-events/1.10.3/1.11.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [eslint-plugin-cypress](https://togithub.com/cypress-io/eslint-plugin-cypress) | [`^2.14.0` -> `^2.15.1`](https://renovatebot.com/diffs/npm/eslint-plugin-cypress/2.14.0/2.15.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [find-cypress-specs](https://togithub.com/bahmutov/find-cypress-specs) | [`^1.35.1` -> `^1.41.4`](https://renovatebot.com/diffs/npm/find-cypress-specs/1.35.1/1.41.4) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>cypress-io/code-coverage (@​cypress/code-coverage)</summary> ### [`v3.12.18`](https://togithub.com/cypress-io/code-coverage/releases/tag/v3.12.18) [Compare Source](https://togithub.com/cypress-io/code-coverage/compare/v3.12.17...v3.12.18) ##### Bug Fixes - **deps:** update dependency [@​types/react](https://togithub.com/types/react) to v18.2.47 ([#​762](https://togithub.com/cypress-io/code-coverage/issues/762)) ([4ab9fb1]( |
||
|
53c3907529
|
[ML] Add support for ES|QL in Data visualizer (#174188)
## Summary This PR adds support for ES|QL queries in Data visualizer. <img width="1695" alt="Screenshot 2024-01-26 at 17 07 59" src=" |
||
|
4a92a8832f
|
[ES|QL] Use same adhoc dataviews for queries with the same index pattern (#174736) | ||
|
ca23dd5060
|
[SecuritySolution] Remove remaining usage of redux-observable (#175678)
## Summary In this PR, we're removing all usages of `redux-observable` in favor of simple middlewares. This work is part of [this tech debt ticket](https://github.com/elastic/kibana/issues/175427) which outlines the motivation of this move. A couple shortcuts had to be taken and I added comments further down to explain the motivation. ### Oddities Weirdly, the CI reports an increase in async chunks, instead of an expected decrease due to removing a library. | id | [before]( |
||
|
0e22f756b7
|
[Reporting] Puppeteer v21.9.0 upgrade (#175835)
## Summary Upgrades Puppeteer to version 21.9.0 <!-- ### Checklist Delete any items that are not applicable to this PR. - [ ] 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/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Multiple Spaces—unexpected behavior in non-default Kibana Space. | Low | High | Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces. | | Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. | High | Low | Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure. | | Code should gracefully handle cases when feature X or plugin Y are disabled. | Medium | High | Unit tests will verify that any feature flag or plugin combination still results in our service operational. | | [See more potential risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) | ### 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) --> |
||
|
447cd44bf2
|
Upgrade EUI to v92.2.1 (#175849)
`v92.1.1`⏩`v92.2.1` --- ## [`v92.2.1`](https://github.com/elastic/eui/releases/v92.2.1) **Bug fixes** - Removed unintentional i18n tokens in prior release that should not have been exported ## [`v92.2.0`](https://github.com/elastic/eui/releases/v92.2.0) - Updated `EuiFlyoutResizable` with new optional `onResize` callback ([#7464](https://github.com/elastic/eui/pull/7464)) **Bug fixes** - Fixed an issue in `EuiResizableContainer` where `onResizeEnd` could become a stale closure when renders occured between resize start and end, resulting in an outdated version of a consumer's `onResizeEnd` callback being called ([#7468](https://github.com/elastic/eui/pull/7468)) - Fixed `EuiTextArea` to correctly fire `onChange` callbacks on clear button click ([#7473](https://github.com/elastic/eui/pull/7473)) - Fixed `EuiContextMenu`'s panel titles & items to not show underlines on hover for non-interactive elements ([#7474](https://github.com/elastic/eui/pull/7474)) **Deprecations** - Remove unused public `EuiHue` and `EuiSaturation` subcomponent exports. Use the parent `EuiColorPicker` component instead ([#7460](https://github.com/elastic/eui/pull/7460)) - Remove unused public `EuiCommentTimeline` subcomponent export. Use the parent `EuiComment` or `EuiCommentList` components instead. ([#7467](https://github.com/elastic/eui/pull/7467)) |
||
|
92052864a8
|
Upgrade selenium-webdriver to 4.17.0 (#175746)
Will be testing as a fix for https://github.com/elastic/kibana/pull/175740 |
||
|
85013e943b
|
chore(NA): add sharp resolution for v0.32.6 (#175720)
Closes https://github.com/elastic/kibana/issues/175544 I think what we were seeing around the sharp issue was the same problem of other native modules which is the install step not running and installing the correct native binaries because of corrupted caches when changing branches. Currently moving to v0.33+ will be problematic because we are using yarn v1 so this PR is making a resolution pin which will help on not making the upgrade for the moment as well as to a correct dep installation when resetting the environment. |
||
|
5257607869
|
Update dependency sass-embedded to ^1.70.0 (main) (#173230)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [sass-embedded](https://togithub.com/sass/embedded-host-node) | [`^1.69.5` -> `^1.70.0`](https://renovatebot.com/diffs/npm/sass-embedded/1.69.5/1.70.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>sass/embedded-host-node (sass-embedded)</summary> ### [`v1.70.0`](https://togithub.com/sass/embedded-host-node/blob/HEAD/CHANGELOG.md#1700) [Compare Source](https://togithub.com/sass/embedded-host-node/compare/1.69.7...1.70.0) ##### JavaScript API - Add a `sass.initCompiler()` function that returns a `sass.Compiler` object which supports `compile()` and `compileString()` methods with the same API as the global Sass object. On the Node.js embedded host, each `sass.Compiler` object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient. - Add a `sass.initAsyncCompiler()` function that returns a `sass.AsyncCompiler` object which supports `compileAsync()` and `compileStringAsync()` methods with the same API as the global Sass object. On the Node.js embedded host, each `sass.AsynCompiler` object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient. ##### Embedded Sass - Support the `CompileRequest.silent` field. This allows compilations with no logging to avoid unnecessary request/response cycles. - The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's `info` field. ### [`v1.69.7`](https://togithub.com/sass/embedded-host-node/blob/HEAD/CHANGELOG.md#1697) [Compare Source](https://togithub.com/sass/embedded-host-node/compare/1.69.6...1.69.7) ##### Embedded Sass - In the JS Embedded Host, properly install the x64 Dart Sass executable on ARM64 Windows. ### [`v1.69.6`](https://togithub.com/sass/embedded-host-node/blob/HEAD/CHANGELOG.md#1696) [Compare Source](https://togithub.com/sass/embedded-host-node/compare/1.69.5...1.69.6) - Produce better output for numbers with complex units in `meta.inspect()` and debugging messages. - Escape U+007F DELETE when serializing strings. - When generating CSS error messages to display in-browser, escape all code points that aren't in the US-ASCII region. Previously only code points U+0100 LATIN CAPITAL LETTER A WITH MACRON were escaped. - Provide official releases for musl LibC and for Android. - Don't crash when running `meta.apply()` in asynchronous mode. ##### JS API - Fix a bug where certain exceptions could produce `SourceSpan`s that didn't follow the documented `SourceSpan` API. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/elastic/kibana). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44Ny4yIiwidXBkYXRlZEluVmVyIjoiMzcuMTM1LjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Jonathan Budzenski <jon@elastic.co> |
||
|
35e7325753
|
Rename log_explorer and observability_log_explorer plugins (#175510)
- Rename `log_explorer` to `logs_explorer` and move it to an `observability_solution` subfolder - Rename `observability_log_explorer` to `observability_logs_explorer` and move it to an `observability_solution` subfolder - Use `renameFromRoot` to rename old configs Related to https://github.com/elastic/kibana/issues/171991 and https://github.com/elastic/kibana/pull/170759 This PR is mostly focused on renaming the plugins, follow ups will be created to change mentions of `log explorer`, `logExplorer` etc. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com> |
||
|
dade4f1d54
|
Add ResizeObserver polyfill globally in Jest tests (#173772)
## Summary This PR adds the ResizeObserver polyfill in Jest Tests reusing a polyfill already used in Kibana. The PR also removes all the mocks for the ResizeObserver used in tests. The polyfill is no longer needed in code running on a browser as the [ResizeObserver API is already available](https://developer.mozilla.org/en-US/docs/Web/API/ResizeObserver#browser_compatibility) in every Kibana-supported browser. There is still one last polyfill to remove `@juggle/resize-observer` but this is used internally by the `use-resize-observer` hook. A following PR could probably replace that hook with a different hook that doesn't require that polyfill to cleanup a bit our dependencies |
||
|
b0a0eee9ce
|
Revert upgrade to axios@1.6.5 and follow-redirects@1.15.4 (#175496)
## Summary Due to a [known issue](https://github.com/axios/axios/issues/6179) with axios > 1.6.3 and follow-redirects > 1.15.3, this PR reverts a recent upgrade to both libraries by adding resolutions in the package file, and removing the caret range for axios. This is meant to be a temporary measure - once the known issue is resolved, these changes must be reverted. |
||
|
b25407edba
|
Update Kibana code editor dependencies (#171720)
## Summary This PR started out as an attempt to resolve https://github.com/elastic/kibana/issues/166559; which it does, the appropriate colours for the message prompt displayed when an edit attempt on read only content is made in the code editor for both dark and light mode are now set; ### Light mode <img width="412" alt="Screenshot 2023-11-22 at 11 30 17" src=" |
||
|
2f8825d68a
|
Upgrade EUI to v92.1.1 (#174955)
`v92.0.0-backport.0`⏩ `v92.1.1` --- ## [`v92.1.1`](https://github.com/elastic/eui/releases/v92.1.1) **Bug fixes** - Minor `EuiDataGrid` cell performance fixes ([#7465](https://github.com/elastic/eui/pull/7465)) ## [`v92.1.0`](https://github.com/elastic/eui/releases/v92.1.0) - Updated `EuiResizableButton` to allow customizing the `indicator` style with either `handle` (default) or `border` ([#7455](https://github.com/elastic/eui/pull/7455)) - Enhanced `EuiResizableContainer` to preserve the drag/resize event when the user's mouse leaves the parent container and re-enters ([#7456](https://github.com/elastic/eui/pull/7456)) **Bug fixes** - Fixed an `EuiTreeView` JSX Typescript error ([#7452](https://github.com/elastic/eui/pull/7452)) - Fixed a color console warning being generated by disabled `EuiStep`s ([#7454](https://github.com/elastic/eui/pull/7454)) **Accessibility** - `EuiDataGrid`'s keyboard/screenreader experience has been tweaked to be more consistent for varying complex data: ([#7448](https://github.com/elastic/eui/pull/7448)) - Headers are now always navigable by arrow key, regardless of whether the header cells contain interactive content - Non-expandable cells containing any amount of interactive content now must be entered via Enter or F2 keypress - Expandable cells continue to be toggled via Enter or F2 keypress - `EuiDataGrid` now provides a direct screen reader hint for Enter key behavior for expandable & interactive cells ([#7448](https://github.com/elastic/eui/pull/7448)) |
||
|
cd907739f3
|
fix(x-pack/reporting): use FIPS-compliant ID generator uuidv4 in Reporting plugin (#174809)
## Summary Closes #174798 ### Checklist Delete any items that are not applicable to this PR. ### Risk Matrix Delete this section if it is not applicable to this PR. ### 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) --------- Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
a63bb6add0
|
[Security Solution] Data quality dashboard persistence (#173185)
## Summary issue https://github.com/elastic/security-team/issues/7382 ### Data Stream Adapter This PR introduces the `@kbn/data-stream-adapter` package, which is a utility library to facilitate Data Stream creation and maintenance in Kibana, it was inspired by the data stream implementation in the Alerts plugin. The library has two exports: - `DataStreamSpacesAdapter`: to manage space data streams. It uses the `name-of-the-data-stream-<spaceId>` naming pattern. - `DataStreamAdapter`: to manage single (not space-aware) data streams. Usage examples in the package [README]( |
||
|
6c5109e58b
|
Upgrade @adobe/css-tools to 4.3.2 (#175364)
## Summary Upgrade `@adobe/css-tools` from `v4.3.1` to `v4.3.2` |
||
|
1d4b7df989
|
[Lens] Prevent overwriting managed content from editor (#175062)
## Summary Close https://github.com/elastic/kibana/issues/166720 I marked this a breaking change since it is preventing users from doing something they have been able to do before. They can no longer save changes to managed Lens visualizations. Instead, they have to save changes to a new visualization. To test, import this `ndjson` file which includes both a managed and an unmanaged visualization: --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
5f72e78f82
|
[Dev] Add High Cardinality Indexer to Kibana as kbn-data-forge (#174559)
## Summary This PR adds the [High Cardinality Indexer](https://github.com/elastic/high-cardinality-cluster) to Kibana as a new package called `kbn-data-forge`. It also replaces `kbn-infra-forge` usage in the test and is the preferred way to generate data for Observability use cases, specifically for SLO testing. ### Todo - [x] Replace `kbn-infra-forge` usage - [x] Create convenience functions for testing (`generate` and `cleanup`) - [x] Make the logger (`LoggingTool`) configurable as an injected dependency - [x] Make the Elasticsearch client (`Client`) configurable as an injected dependency - [x] Fix the ECS Generate commands - [x] Add CLI options via Commander ### CLI Help Screen ``` Usage: data_forge.js [options] A data generation tool that will create realistic data with different scenarios. Options: --config <filepath> The YAML config file --lookback <datemath> When to start the indexing (default: "now-15m") --events-per-cycle <number> The number of events per cycle (default: 1) --payload-size <number> The size of the ES bulk payload (default: 10000) --concurrency <number> The number of concurrent connections to Elasticsearch (default: 5) --index-interval <milliseconds> The interval of the data in milliseconds (default: 60000) --dataset <dataset> The name of the dataset to use. Valid options: "fake_logs", "fake_hosts", "fake_stack" (default: "fake_logs") --scenario <scenerio> The scenario to label the events with (default: "good") --elasticsearch-host <address> The address to the Elasticsearch cluster (default: "http://localhost:9200") --elasticsearch-username <username> The username to for the Elasticsearch cluster (default: "elastic") --elasticsearch-password <password> The password for the Elasticsearch cluster (default: "changeme") --elasticsearch-api-key <key> The API key to connect to the Elasticsearch cluster --kibana-url <address> The address to the Kibana server (default: "http://localhost:5601") --kibana-username <username> The username for the Kibana server (default: "elastic") --kibana-password <password> The password for the Kibana server (default: "changeme") --install-kibana-assets This will install index patterns, visualizations, and dashboards for the dataset --event-template <template> The name of the event template (default: "good") --reduce-weekend-traffic-by <ratio> This will reduce the traffic on the weekends by the specified amount. Example: 0.5 will reduce the traffic by half (default: 0) --ephemeral-project-ids <number> The number of ephemeral projects to create. This is only enabled for the "fake_stack" dataset. It will create project IDs that will last 5 to 12 hours. (default: 0) -h, --help output usage information ``` ### Testing an Example Run the following command against a clean Kibana development enviroment: ``` node x-pack/scripts/data_forge.js --events-per-cycle 200 --lookback now-1h --install-kibana-assets --ephemeral-project-ids 10 --dataset fake_stack ``` This should install a handful of DataViews (Admin Console, Message Processor, Nginx Logs, Mongodb Logs) along with a few dashboards and visualizations. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
73e5a96922
|
[Lens] Datatable improvements (#174994)
## Summary Fixes #160719 and #164413 This PR contains some work about Lens datatable, here's a short list: * moved out the sorting logic of the datatable into an independent package: `@kbn/sort-predicates` * leverage the EUI Datagrid `schemaDetectors` for the table rows sorting * apply datatable columns sorting also to the CSV exporter ### 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 --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
b0ef006df3
|
Update dependency elastic-apm-node to ^4.4.0 (main) (#175174)
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [elastic-apm-node](https://togithub.com/elastic/apm-agent-nodejs) | [`^4.3.0` -> `^4.4.0`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.3.0/4.4.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>elastic/apm-agent-nodejs (elastic-apm-node)</summary> ### [`v4.4.0`](https://togithub.com/elastic/apm-agent-nodejs/releases/tag/v4.4.0) [Compare Source](https://togithub.com/elastic/apm-agent-nodejs/compare/v4.3.0...v4.4.0) For more information, please see the [changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.4.0). ##### Elastic APM Node.js agent layer ARNs |Region|ARN| |------|---| |af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-4-0:1| |us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-4-0:1| </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/elastic/kibana). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMzUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEzNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
44e987271f
|
Upgrade @reduxjs/toolkit to v1.9.7 (#175017)
## Summary Follow up to #138818. This updates Redux Toolkit to the latest version right before v2. It also updates dependencies of Redux Toolkit that are also in `package.json` to match the version used in Redux Toolkit. - Upgrades `@reduxjs/toolkit` from `v1.7.2` to `v1.9.7`. - Upgrades `immer` from `v9.0.15` to `v9.0.21`. - Upgrades `redux` from `v4.2.0` to `v4.2.1`. - Upgrades `redux-thunk` from `v2.4.1` to `v2.4.2`. - Upgrades `reselect` from `v4.1.6` to `v4.1.8`. ### Checklist - [x] 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) |
||
|
2f92ce1d4a
|
[dx] Dependency check script for plugins (#171483)
## Summary Dealing with circular dependencies between plugins has become a sharp pain point for anyone developing plugins in Kibana. ### Providing dependencies to a plugin First, a plugin defines its dependencies in its `kibana.jsonc` file as one of three types: - `required` - the dependency must be present and enabled -- will be guaranteed in the lifecycle - `optional` - the dependency can be missing or disabled -- will be `undefined` in the lifecycle - `requiredBundle` - the dependency is required as static code only -- will not be present in the lifecycle Missing or circular dependencies are detected by the Kibana platform when it starts. ### Providing dependencies in code Our plugins are written in and type-checked by Typescript. As such, each plugin needs to maintain Typescript types defining what the platform is providing. This is done manually, and there is no enforcement mechanism between that and the plugin Typescript types. If these dependency definitions are inconsistent or stale, it can lead to host of issues: - optional plugins typed as required that are disabled crash the plugin at runtime; - plugins that are no longer used still included in dependency checks; - plugins marked as required or optional that are actually required bundles. - etc. ### Dependencies with side-effects One of the interesting things that has come out of this has been identifying plugins that provide dependent logic through side-effects, rather than lifecycles. As an example, `licensing` provides a lifecycle contracts, but also a [route handler context](https://github.com/elastic/kibana/blob/main/x-pack/plugins/licensing/server/licensing_route_handler_context.ts) as middleware for a dependent plugin. Unfortunately, while this dependency can be stated as `required` in a dependent plugin's `kibana.jsonc`, the fact that this is a side-effect makes it incredible difficult to understand the dependency without searching the code. <img width="735" alt="Screenshot 2023-12-13 at 10 08 00 AM" src=" |
||
|
64ebaffd89
|
[Embeddable Refactor] Create Decoupled Presentation Panel (#172017)
Closes https://github.com/elastic/kibana/issues/167426 Closes https://github.com/elastic/kibana/issues/167890 Contains much of the prep work required to decouple the Embeddables system from Kibana in anticipation of its deprecation and removal. Co-authored-by: Nathan Reese <reese.nathan@gmail.com> |
||
|
6499bcd370
|
[Security] Security/Buildkite Analytics test suites integration (#174524)
## Summary This PR introduces the integration of the following categories of tests with Buildkite Test Suites. - Security Solution Cypress - [Buildkite test suite](https://buildkite.com/organizations/elastic/analytics/suites/ci-security-solution-cypress?branch=all+branches) - Defend Workflows - [Buildkite test suite](https://buildkite.com/organizations/elastic/analytics/suites/ci-defend-workflows?branch=all+branches) - Threat Intelligence - [Buildkite test suite](https://buildkite.com/organizations/elastic/analytics/suites/ci-threat-intelligence?branch=all+branches) - Serverless Security Solution Cypress - [Buildkite test suite](https://buildkite.com/organizations/elastic/analytics/suites/serverless-security-solution-cypress-1?branch=all+branches) It also addresses a wrong package.json script invocation and the parallelism that is used in the pipeline which was reduced for some targets. Check File: .buildkite/pipelines/security_solution/security_solution_cypress.yml ## Initial PR https://github.com/elastic/kibana/pull/173005 - Status Closed |
||
|
2f85d12f65
|
Revert "Upgrade axios@1.6.3→1.6.5" (#174794)
Reverts elastic/kibana#174642 Reverts elastic/kibana#174312 There is a [known issue](https://github.com/axios/axios/issues/6179) with `axios`@>=1.6.4 and `follow-redirects`@>=1.15.4. |
||
|
7bee86d6eb
|
Add Mock IDP login page and role switcher (#172257) | ||
|
45efaad8ed
|
Upgrade axios@1.6.3→1.6.5 (#174642)
## Summary Upgrades `axios` from v1.6.3 to v1.6.5. |
||
|
517763e037
|
Upgrade EUI to v92.0.0 (#174487)
`v91.3.1`⏩`v92.0.0-backport.0` --- ## [`v92.0.0-backport.0`](https://github.com/elastic/eui/releases/v92.0.0-backport.0) **This is a backport release only intended for use by Kibana.** **Bug fixes** - Fixed an `EuiTreeView` JSX Typescript error ([#7452](https://github.com/elastic/eui/pull/7452)) - Fixed a color console warning being generated by disabled `EuiStep`s ([#7454](https://github.com/elastic/eui/pull/7454)) ## [`v92.0.0`](https://github.com/elastic/eui/releases/v92.0.0) - Updated generic types of `EuiBasicTable`, `EuiInMemoryTable` and `EuiSearchBar.Query.execute` to add `extends object` constraint ([#7340](https://github.com/elastic/eui/pull/7340)) - This change should have no impact on your applications since the updated types only affect properties that exclusively accept object values. - Added a new `EuiFlyoutResizable` component ([#7439](https://github.com/elastic/eui/pull/7439)) - Updated `EuiTextArea` to accept `isClearable` and `icon` as props ([#7449](https://github.com/elastic/eui/pull/7449)) **Bug fixes** - `EuiRange`/`EuiDualRange`'s track ticks & highlights now update their positions on resize ([#7442](https://github.com/elastic/eui/pull/7442)) **Deprecations** - Updated `EuiFilterButton` to remove the second `.euiFilterButton__textShift` span wrapper. Target `.euiFilterButton__text` instead ([#7444](https://github.com/elastic/eui/pull/7444)) **Breaking changes** - Removed deprecated `EuiNotificationEvent`. We recommend copying the component to your application if necessary ([#7434](https://github.com/elastic/eui/pull/7434)) - Removed deprecated `EuiControlBar`. We recommend using `EuiBottomBar` instead ([#7435](https://github.com/elastic/eui/pull/7435)) |
||
|
46707e46de
|
[FTR] Mv test subjs svc to shared location (#174048)
## Summary Refactoring general ui service to a kbn package. --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
de961a54a7
|
Remove Gainsight from cloud plugin (#172318)
## Summary - Remove gainsight plugin from cloud plugin - add config deprecation in fullstory Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
30638cd762
|
[Lens] [Datatable] toolbar tests rewritten to testing-library/react (#173075)
## Summary Rewrites datatable toolbar tests to testing-library. It also starts a new package – shared space to park EUI component test helpers that we eventually donate to EUI for ongoing maintenance. So far it's just one helper but hopefully we'll be adding helpers soon! |
||
|
64ea66731b
|
Update APM (main) (#174157)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@elastic/apm-rum](https://togithub.com/elastic/apm-agent-rum-js)
([source](https://togithub.com/elastic/apm-agent-rum-js/tree/HEAD/packages/rum))
| [`^5.15.0` ->
`^5.16.0`](https://renovatebot.com/diffs/npm/@elastic%2fapm-rum/5.15.0/5.16.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
|
[@elastic/apm-rum-react](https://www.elastic.co/guide/en/apm/agent/rum-js/current/index.html)
([source](https://togithub.com/elastic/apm-agent-rum-js/tree/HEAD/packages/rum-react))
| [`^2.0.1` ->
`^2.0.2`](https://renovatebot.com/diffs/npm/@elastic%2fapm-rum-react/2.0.1/2.0.2)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>elastic/apm-agent-rum-js (@​elastic/apm-rum)</summary>
###
[`v5.16.0`](https://togithub.com/elastic/apm-agent-rum-js/blob/HEAD/packages/rum/CHANGELOG.md#5160-2023-12-27)
[Compare
Source](https://togithub.com/elastic/apm-agent-rum-js/compare/@elastic/apm-rum@5.15.0...@elastic/apm-rum@5.16.0)
##### Features
- **rum:** report INP metric
([#​1462](https://togithub.com/elastic/apm-agent-rum-js/issues/1462))
([866f066](
|
||
|
159cefacbf
|
Upgrade follow-redirects@1.5.2→1.5.4 (#174312)
## Summary Upgrades follow-redirects from v1.5.2 to v1.5.4. |
||
|
7357af5c1b
|
Upgrade EUI to v91.3.1 (#173569)
`v91.0.0-backport.0`⏩`v91.3.1` ⚠️ The largest set of changes in this PR that touch source code (as opposed to test code) are related to several **EuiDataGrid** redesigns, particularly around the toolbar, column cell headers, and cell actions. We **strongly** recommend QAing your EuiDataGrid usages, **especially** if you have custom CSS styling on data grid cells. | Changes | Screencap | |--------|--------| | Cell actions and popover | <img src=" |
||
|
d458b5382f
|
Remove legacy kibana react code editor (#171047)
## Summary
This PR removes the legacy kibana react code-editor, alongside replacing
all import declarations of this legacy component to the one offered by
shared-ux, i.e import declaration source of `'@kbn/kibana-react/public'`
is switched to `@kbn/code-editor`.
Also in this PR an helper for writing jest tests has been included
through the package `@kbn/code-editor-mock`, this would facilitate
mocking the editor, especially given that the code editor leverages
couple of APIs that are aren't included by default in jsdom, among them,
`matchMedia`, `ResizeObserver`. The provided mock is sufficient for most
use cases and can be setup in any package within kibana as a
[`node_module`
mock](https://jestjs.io/docs/manual-mocks#mocking-node-modules) without
having to repeatedly manually mock the editor within individual test
files. An example for how this might be done can be found here
|