…on-206439
* main: (402 commits)
[Search]: Fix Number type field to have correct property (elastic#210462)
Change filter for rule monitoring gaps (elastic#209983)
Update Logs Explorer deprecation messages (elastic#201307)
[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (elastic#210613)
[Embeddable] Fix presentation panel styles (elastic#210113)
[ci] enable Scout reporter for on-merge-unsupported-ftrs (elastic#210627)
[Fix][Synonyms UI]Add navigation link to the Detail breadcrumb. (elastic#209574)
chore(dep): bump `store2` from `2.12.0` to `2.14.4` (elastic#210530)
[scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (elastic#209761)
[Cloud Security] Asset Inventory table flyout controls (elastic#208452)
[ML] Fix model deployment check in file uploader (elastic#209585)
Updates archive again (elastic#209828)
[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (elastic#209551)
[Search] [Onboarding] Update search api to use EventEmitter instead of Provider (elastic#209784)
[maps] lazy load map actions (elastic#210252)
[Cloud Security] Adding telemetry collection condition based on render condition (elastic#208758)
[Solution nav] Use flyout for Stack Management in Search and Observability solutions (elastic#208632)
[Search] Fix Add Inference Endpoint API call (elastic#210243)
[Agentless Connectors] Integration overview panel (elastic#210222)
[Lens] Restore dynamic colouring by value for Last value agg (elastic#209110)
...
Summary
Transitions API key state management from a provider to an event emitter, simplifying integration and eliminating the need to wrap components in context. Components can now directly call useSearchApiKey().
Fixes an issue where invalidated API keys were not automatically regenerated. The new approach ensures that the key is properly recreated, improving the reliability of API key handling.
Added/Updated FTRs for those changes
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.