[Security Solution] Use static declaration for navigation hierarchy by tsullivan · Pull Request #215969 · elastic/kibana

tsullivan · 2025-03-25T22:47:21Z

Summary

Part of Epic: https://github.com/elastic/kibana-team/issues/1439
Addresses #212903, but does not remove the landing page access. The landing page access will be removed in #210893

Changes

Converts the declaration of the Security Solution side navigation for serverless and stateful projects into a static declaration, rather than algorithmically parsing registered links to dynamically build the declaration.
Updates the contents of the "Assets" panel to prepare for removal of that landing page.
Eliminates the top-level nesting of the nav items, which removes the extra space between the project title and the first nav items. See 45454bd

Known issue: Clicking the "Browse integrations" button does not close the secondary nav panel. Doing that will be a relatively simple chore, but will require some changes in the SharedUX chrome-navigation package, as well as the LinkButton component in the Security Solution navigation-links package.

Screenshots

Serverless

Stateful/ECH

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Unit or functional tests were updated or added to match the most common scenarios

…fix'

tsullivan · 2025-03-27T19:21:59Z

x-pack/test/security_solution_cypress/cypress/e2e/explore/navigation/navigation.cy.ts

-  it('navigates to the Fleet page', () => {
-    navigateFromHeaderTo(ServerlessHeaders.FLEET, true);
-    cy.url().should('include', FLEET_URL);
-  });


Per @paulewing, the removal of Fleet from the primary nav "was purposeful to focus those asset mngmt workflows in a single asset UX"

...tform/packages/shared/shared-ux/chrome/navigation/src/ui/components/panel/panel_nav_item.tsx

tomsonpl

Sad to see my AI_SOC changes go away after just a week ;) but it looks great and also tested locally and it all works great 👍
Thanks!

elasticmachine · 2025-04-02T18:23:22Z

💚 Build Succeeded

Buildkite Build
Commit: 182abaf

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`securitySolution`	7176	7171	-5
`securitySolutionEss`	93	95	+2
total			-3

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`securitySolution`	128	127	-1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`securitySolution`	8.9MB	8.9MB	-10.9KB
`securitySolutionEss`	36.0KB	34.9KB	-1.1KB
total			-12.0KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`securitySolution`	35	34	-1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`securitySolution`	88.8KB	88.8KB	-57.0B
`securitySolutionEss`	15.5KB	34.4KB	+18.9KB
`securitySolutionServerless`	35.0KB	51.3KB	+16.3KB
total			+35.1KB

Unknown metric groups

API count

id	before	after	diff
`securitySolution`	196	195	-1

async chunk count

id	before	after	diff
`securitySolution`	126	124	-2

History

💚 Build #289284 succeeded 5a5e9a6
💔 Build #289276 failed 45454bd
💔 Build #289265 failed 297ab51
💛 Build #288601 was flaky 8d39f28
💚 Build #288239 succeeded 2efe618
💔 Build #288212 failed 66b5992

cc @tsullivan

semd

LGTM! Thanks Tim

kibanamachine · 2025-04-03T15:38:22Z

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/14247070283

kibanamachine · 2025-04-03T15:44:10Z

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 215969

Questions ?

Please refer to the Backport tool documentation

Part of elastic/kibana-team#1439 Pulled from elastic#210893 elastic#215969 ## Summary 1. Allow item in the secondary panel to use the `renderItem` field 2. Fix handling of `defaultIsCollapsed` for items in the secondary panel 3. Allow secondary panel to contain a mix of ungrouped items as well as sub-groups of items ![alksdjnfgklsdfhglskdhkds](https://github.com/user-attachments/assets/11d316d6-6c9a-4743-897f-93c40efa9013) 4. Fix the flagging of the "active" parent in the main nav panel, based on the current URL ![jhgkdfgkjfhkhn](https://github.com/user-attachments/assets/b5f6efe3-e8f5-494b-bc12-abbd51acc12a) ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [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 (cherry picked from commit 05a8703) # Conflicts: # src/platform/packages/shared/shared-ux/chrome/navigation/src/ui/navigation.stories.tsx

tsullivan · 2025-04-04T18:36:13Z

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

…lastic#215969) ## Summary Part of Epic: elastic/kibana-team#1439 Addresses elastic#212903, but does not remove the landing page access. The landing page access will be removed in elastic#210893 **Changes** 1. Converts the declaration of the Security Solution side navigation for serverless and stateful projects into a static declaration, rather than algorithmically parsing registered links to dynamically build the declaration. 2. Updates the contents of the "Assets" panel to prepare for removal of that landing page. 3. Eliminates the top-level nesting of the nav items, which removes the extra space between the project title and the first nav items. See elastic@45454bd **Known issue**: Clicking the "Browse integrations" button does not close the secondary nav panel. Doing that will be a relatively simple chore, but will require some changes in the SharedUX chrome-navigation package, as well as the `LinkButton` component in the Security Solution navigation-links package. ### Screenshots Serverless ![static-nav-declaration-security-serverless-3iorteikghiskhgkseh](https://github.com/user-attachments/assets/47bcbea9-7e3c-481e-b1b8-4b13bb5d63b1) Stateful/ECH ![static-nav-declaration-security-stateful-3iorteikghiskhgkseh](https://github.com/user-attachments/assets/3d3c8a0e-95d1-4da7-a657-c824577b6ec1) ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [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/main/src/platform/packages/shared/kbn-i18n/README.md) - [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit ef907a3) # Conflicts: # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/ai_soc/ai_soc_navigation.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/side_navigation.ts # x-pack/test/security_solution_cypress/cypress/e2e/explore/navigation/navigation.cy.ts # x-pack/test/security_solution_cypress/cypress/screens/serverless_security_header.ts

kibanamachine · 2025-04-07T15:50:10Z

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

…rchy (#215969) (#217248) # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Use static declaration for navigation hierarchy (#215969)](#215969)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

@tsullivan

## Summary This PR updates and simplifies the general architecture of the Security Solution links, removing unnecessary code. The new architecture leverages the static `navigationTree` files. This approach was discussed and agreed with @tsullivan (Shared-UX team) and introduced in [this PR](#215969). With these changes, the `navigationTree` becomes the SSoT (Single Source of Truth) for the links hierarchy. This is done by registering the Security Solution plugin `deepLinks` using the regular `ApplicationLinks` information, but following the same hierarchy as the `navigationTree`. This ensures consistency across the app and keeps the code DRY. >[!note] These changes only affect the new _Solution navigation_. The _Classic navigation_ remains unchanged and isolated, as it is expected to be deprecated and removed in the near future. ### Architecture change - The "links switchers", which were functions to programmatically change the links hierarchy, have been removed. - The `NavigationLinks` from which we were generating the `navigationTree` programatically have also been dropped. - The SecuritySolution plugin `deepLinks` are now generated using the `ApplicationLinks` for the link configuration (title, path...) and the current `navigationTree` for the hierarchy. #### Previous architecture ![Old Security Serverless links architecture](https://github.com/user-attachments/assets/0c9db269-bd67-4967-9ca1-bec5e874abff) #### New architecture ![New Security Serverless links architecture](https://github.com/user-attachments/assets/9ff24ff8-3ce9-455e-ad76-4baa6b11daa1) >[!important] The landing pages (Rules, Explore, Assets...) were made inaccessible recently by the shared-ux team ([PR](#210893)) in the new Solution navigation as part of an effort to unify with the rest of solutions. This fact also helped simplify the architecture. >[!tip] We have multiple static `navigationTree` definitions, which are used depending on the serverless product tier. Right now, we have the "default" `navigationTree` used in the _essentials_ and _complete_ tiers, and the "AI" `navigationTree` used in the new _searchAiLake_ tier. This approach ensures consistency for the links' locations across Kibana: the "left navigation", the "breadcrumbs", and the "global search" will always be aligned. ### Screenshots #### ECH navigations | Classic nav | Solution nav | |-|-| |<img width="248" alt="classic" src="https://github.com/user-attachments/assets/bb9e722e-316e-4c04-9978-068c35680382" />|<img width="248" alt="solution_nav" src="https://github.com/user-attachments/assets/a993ce49-b780-4405-b829-4d36023ae627" />| #### Serverless navigations | Regular tiers | AI for SOC | |-|-| |<img width="248" alt="regular_serverless_nav" src="https://github.com/user-attachments/assets/d782bf49-6c76-4414-a807-35245a5e9883" />|<img width="248" alt="ai_nav" src="https://github.com/user-attachments/assets/25d9950d-77c8-4d44-ab53-4b07423713af" />| #### Example of hierarchy for the `Endpoints` page: ##### Classic nav ![classic_nav_hierarchy](https://github.com/user-attachments/assets/d4c41c0a-f24f-469d-843c-10ff5b3c5174) ##### Solution nav ![solution_nav_hierarchy](https://github.com/user-attachments/assets/e7f753e2-a499-4130-9bd0-9d22788d612b) ### Other changes - `NavLinks` are no longer used by the Solution navigation and have been deprecated. They are only used in the Classic navigation now and will be removed along with it. - `ExternalPageNames` are no longer used and have been removed. - `ApplicationLinks` observables moved to a singleton class. - Link-related hooks have been moved to their own `links_hooks.ts` file. ### Next steps When the Classic navigation is deprecated, we'll be able to: - Define a flat structure of `ApplicationLinks` and remove the concept of `category` in them. - Remove Classic Security navigation components. - Remove all the landing pages and their components in the navigation package. The [docs](https://docs.elastic.dev/security-solution/dev-docs/app-links) will be updated once this is merged. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@tsullivan

…c#217890) ## Summary This PR updates and simplifies the general architecture of the Security Solution links, removing unnecessary code. The new architecture leverages the static `navigationTree` files. This approach was discussed and agreed with @tsullivan (Shared-UX team) and introduced in [this PR](elastic#215969). With these changes, the `navigationTree` becomes the SSoT (Single Source of Truth) for the links hierarchy. This is done by registering the Security Solution plugin `deepLinks` using the regular `ApplicationLinks` information, but following the same hierarchy as the `navigationTree`. This ensures consistency across the app and keeps the code DRY. >[!note] These changes only affect the new _Solution navigation_. The _Classic navigation_ remains unchanged and isolated, as it is expected to be deprecated and removed in the near future. ### Architecture change - The "links switchers", which were functions to programmatically change the links hierarchy, have been removed. - The `NavigationLinks` from which we were generating the `navigationTree` programatically have also been dropped. - The SecuritySolution plugin `deepLinks` are now generated using the `ApplicationLinks` for the link configuration (title, path...) and the current `navigationTree` for the hierarchy. #### Previous architecture ![Old Security Serverless links architecture](https://github.com/user-attachments/assets/0c9db269-bd67-4967-9ca1-bec5e874abff) #### New architecture ![New Security Serverless links architecture](https://github.com/user-attachments/assets/9ff24ff8-3ce9-455e-ad76-4baa6b11daa1) >[!important] The landing pages (Rules, Explore, Assets...) were made inaccessible recently by the shared-ux team ([PR](elastic#210893)) in the new Solution navigation as part of an effort to unify with the rest of solutions. This fact also helped simplify the architecture. >[!tip] We have multiple static `navigationTree` definitions, which are used depending on the serverless product tier. Right now, we have the "default" `navigationTree` used in the _essentials_ and _complete_ tiers, and the "AI" `navigationTree` used in the new _searchAiLake_ tier. This approach ensures consistency for the links' locations across Kibana: the "left navigation", the "breadcrumbs", and the "global search" will always be aligned. ### Screenshots #### ECH navigations | Classic nav | Solution nav | |-|-| |<img width="248" alt="classic" src="https://github.com/user-attachments/assets/bb9e722e-316e-4c04-9978-068c35680382" />|<img width="248" alt="solution_nav" src="https://github.com/user-attachments/assets/a993ce49-b780-4405-b829-4d36023ae627" />| #### Serverless navigations | Regular tiers | AI for SOC | |-|-| |<img width="248" alt="regular_serverless_nav" src="https://github.com/user-attachments/assets/d782bf49-6c76-4414-a807-35245a5e9883" />|<img width="248" alt="ai_nav" src="https://github.com/user-attachments/assets/25d9950d-77c8-4d44-ab53-4b07423713af" />| #### Example of hierarchy for the `Endpoints` page: ##### Classic nav ![classic_nav_hierarchy](https://github.com/user-attachments/assets/d4c41c0a-f24f-469d-843c-10ff5b3c5174) ##### Solution nav ![solution_nav_hierarchy](https://github.com/user-attachments/assets/e7f753e2-a499-4130-9bd0-9d22788d612b) ### Other changes - `NavLinks` are no longer used by the Solution navigation and have been deprecated. They are only used in the Classic navigation now and will be removed along with it. - `ExternalPageNames` are no longer used and have been removed. - `ApplicationLinks` observables moved to a singleton class. - Link-related hooks have been moved to their own `links_hooks.ts` file. ### Next steps When the Classic navigation is deprecated, we'll be able to: - Define a flat structure of `ApplicationLinks` and remove the concept of `category` in them. - Remove Classic Security navigation components. - Remove all the landing pages and their components in the navigation package. The [docs](https://docs.elastic.dev/security-solution/dev-docs/app-links) will be updated once this is merged. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

@tsullivan

…c#217890) ## Summary This PR updates and simplifies the general architecture of the Security Solution links, removing unnecessary code. The new architecture leverages the static `navigationTree` files. This approach was discussed and agreed with @tsullivan (Shared-UX team) and introduced in [this PR](elastic#215969). With these changes, the `navigationTree` becomes the SSoT (Single Source of Truth) for the links hierarchy. This is done by registering the Security Solution plugin `deepLinks` using the regular `ApplicationLinks` information, but following the same hierarchy as the `navigationTree`. This ensures consistency across the app and keeps the code DRY. >[!note] These changes only affect the new _Solution navigation_. The _Classic navigation_ remains unchanged and isolated, as it is expected to be deprecated and removed in the near future. ### Architecture change - The "links switchers", which were functions to programmatically change the links hierarchy, have been removed. - The `NavigationLinks` from which we were generating the `navigationTree` programatically have also been dropped. - The SecuritySolution plugin `deepLinks` are now generated using the `ApplicationLinks` for the link configuration (title, path...) and the current `navigationTree` for the hierarchy. #### Previous architecture ![Old Security Serverless links architecture](https://github.com/user-attachments/assets/0c9db269-bd67-4967-9ca1-bec5e874abff) #### New architecture ![New Security Serverless links architecture](https://github.com/user-attachments/assets/9ff24ff8-3ce9-455e-ad76-4baa6b11daa1) >[!important] The landing pages (Rules, Explore, Assets...) were made inaccessible recently by the shared-ux team ([PR](elastic#210893)) in the new Solution navigation as part of an effort to unify with the rest of solutions. This fact also helped simplify the architecture. >[!tip] We have multiple static `navigationTree` definitions, which are used depending on the serverless product tier. Right now, we have the "default" `navigationTree` used in the _essentials_ and _complete_ tiers, and the "AI" `navigationTree` used in the new _searchAiLake_ tier. This approach ensures consistency for the links' locations across Kibana: the "left navigation", the "breadcrumbs", and the "global search" will always be aligned. ### Screenshots #### ECH navigations | Classic nav | Solution nav | |-|-| |<img width="248" alt="classic" src="https://github.com/user-attachments/assets/bb9e722e-316e-4c04-9978-068c35680382" />|<img width="248" alt="solution_nav" src="https://github.com/user-attachments/assets/a993ce49-b780-4405-b829-4d36023ae627" />| #### Serverless navigations | Regular tiers | AI for SOC | |-|-| |<img width="248" alt="regular_serverless_nav" src="https://github.com/user-attachments/assets/d782bf49-6c76-4414-a807-35245a5e9883" />|<img width="248" alt="ai_nav" src="https://github.com/user-attachments/assets/25d9950d-77c8-4d44-ab53-4b07423713af" />| #### Example of hierarchy for the `Endpoints` page: ##### Classic nav ![classic_nav_hierarchy](https://github.com/user-attachments/assets/d4c41c0a-f24f-469d-843c-10ff5b3c5174) ##### Solution nav ![solution_nav_hierarchy](https://github.com/user-attachments/assets/e7f753e2-a499-4130-9bd0-9d22788d612b) ### Other changes - `NavLinks` are no longer used by the Solution navigation and have been deprecated. They are only used in the Classic navigation now and will be removed along with it. - `ExternalPageNames` are no longer used and have been removed. - `ApplicationLinks` observables moved to a singleton class. - Link-related hooks have been moved to their own `links_hooks.ts` file. ### Next steps When the Classic navigation is deprecated, we'll be able to: - Define a flat structure of `ApplicationLinks` and remove the concept of `category` in them. - Remove Classic Security navigation components. - Remove all the landing pages and their components in the navigation package. The [docs](https://docs.elastic.dev/security-solution/dev-docs/app-links) will be updated once this is merged. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit c9f2f7c) # Conflicts: # src/platform/packages/shared/deeplinks/security/deep_links.ts # x-pack/platform/plugins/private/translations/translations/fr-FR.json # x-pack/platform/plugins/private/translations/translations/ja-JP.json # x-pack/platform/plugins/private/translations/translations/zh-CN.json # x-pack/solutions/observability/plugins/logs_explorer/.storybook/__mocks__/package_icon.tsx # x-pack/solutions/security/packages/navigation/src/constants.ts # x-pack/solutions/security/packages/navigation/src/i18n_strings.ts # x-pack/solutions/security/packages/navigation/src/navigation_tree/ml_navigation_tree.ts # x-pack/solutions/security/plugins/security_solution/public/app/links/app_links.ts # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/categories.ts # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/links/sections/assets_links.ts # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/links/sections/assets_translations.ts # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/links/sections/lazy_icons.tsx # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/links/sections/ml_links.ts # x-pack/solutions/security/plugins/security_solution/public/app/solution_navigation/links/sections/ml_translations.ts # x-pack/solutions/security/plugins/security_solution/public/common/components/security_route_page_wrapper/index.test.tsx # x-pack/solutions/security/plugins/security_solution/public/common/components/security_route_page_wrapper/index.tsx # x-pack/solutions/security/plugins/security_solution/public/common/utils/timeline/use_show_timeline.test.tsx # x-pack/solutions/security/plugins/security_solution/public/common/utils/timeline/use_show_timeline_for_path.ts # x-pack/solutions/security/plugins/security_solution/public/configurations/routes.tsx # x-pack/solutions/security/plugins/security_solution/public/detections/pages/alert_summary/index.tsx # x-pack/solutions/security/plugins/security_solution/public/lazy_sub_plugins.tsx # x-pack/solutions/security/plugins/security_solution/tsconfig.json # x-pack/solutions/security/plugins/security_solution_ess/public/navigation/__snapshots__/side_navigation.test.tsx.snap # x-pack/solutions/security/plugins/security_solution_ess/public/navigation/side_navigation.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/common/lazy_icons.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/__snapshots__/side_navigation.test.tsx.snap # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/ai_navigation/callout.test.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/ai_navigation/callout.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/ai_navigation/icon.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/ai_navigation/translations.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/index.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/navigation.test.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/security_side_navigation.tsx # x-pack/solutions/security/plugins/security_solution_serverless/public/navigation/side_navigation.ts # x-pack/test/security_solution_cypress/cypress/screens/serverless_security_header.ts

tsullivan force-pushed the fix/security-solution-212903-static-hierarchy branch from 5c99edc to 2eb2a1f Compare March 26, 2025 19:27

This was referenced Mar 26, 2025

[Security Solution navigation] Adapt remaining panels for Solution Nav redesign #213494

Closed

[Security Solution navigation] Adapt Assets panel for Solution Nav redesign #213496

Closed

[Solution Side Nav] Misc UI fixes #216109

Merged

tsullivan force-pushed the fix/security-solution-212903-static-hierarchy branch from 2eb2a1f to 199a249 Compare March 26, 2025 22:14

tsullivan added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SharedUX Platform AppEx-SharedUX (formerly Global Experience) t// labels Mar 26, 2025

tsullivan self-assigned this Mar 26, 2025

tsullivan added the release_note:skip Skip the PR/issue when compiling release notes label Mar 26, 2025

tsullivan and others added 16 commits March 27, 2025 09:47

Fix assets panel

5f8d201

fix cypress tests for nav items under assets

ede95ee

Allow node children to be mix of groups and items

6886478

Fix security solution project nav panels

dd7be70

Static hierarchy definition for Serverless

7866be1

Static hierarchy definition for ESS

374a359

[CI] Auto-commit changed files from 'node scripts/lint_ts_projects --…

7b25b0e

…fix'

fix ts

bee6ab2

update assets

a648326

Fix i18n

b5bad59

restore landing pages

ab5cd8d

fix test

ba40fb9

fix tests

cd2be2a

uncomment storybook FIXME

6552836

Fix cypress tests

1e6f9c5

revert cosmetic storybook change

e241e08

tsullivan force-pushed the fix/security-solution-212903-static-hierarchy branch from feec3f3 to e241e08 Compare March 27, 2025 16:47

tsullivan commented Mar 27, 2025

View reviewed changes

Add “Browse Integrations” callout to Assets panel

448ee58

tsullivan commented Mar 27, 2025

View reviewed changes

...tform/packages/shared/shared-ux/chrome/navigation/src/ui/components/panel/panel_nav_item.tsx Show resolved Hide resolved

increase page load bundle limit for securitySolutionEss

3ff4044

bump limits.yml

5a5e9a6

tomsonpl approved these changes Apr 2, 2025

View reviewed changes

tsullivan added 2 commits April 2, 2025 08:25

reuse code for stack management in serverless

546ba7c

Merge branch 'main' into fix/security-solution-212903-static-hierarchy

182abaf

semd approved these changes Apr 3, 2025

View reviewed changes

semd mentioned this pull request Apr 3, 2025

[ML] Moves job and trained model management features into Stack Management #204290

Merged

9 tasks

tsullivan added backport:version Backport to applied version labels v9.1.0 v8.19.0 and removed backport:prev-major labels Apr 3, 2025

tsullivan merged commit ef907a3 into elastic:main Apr 3, 2025
18 checks passed

kibanamachine mentioned this pull request Apr 4, 2025

[Siem Migrations] Adds separate migration index to store migration metadata #216164

Merged

tsullivan mentioned this pull request Apr 4, 2025

[8.x] [Security Solution] Use static declaration for navigation hierarchy (#215969) #217248

Merged

kibanamachine mentioned this pull request Apr 7, 2025

[Security Solution] Onboarding check inference endpoint #217150

Merged

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Apr 7, 2025

kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Apr 8, 2025

semd mentioned this pull request Apr 11, 2025

[Security Solution] Solution navigation architecture revision #217890

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Security Solution] Use static declaration for navigation hierarchy#215969

[Security Solution] Use static declaration for navigation hierarchy#215969
tsullivan merged 32 commits intoelastic:mainfrom
tsullivan:fix/security-solution-212903-static-hierarchy

tsullivan commented Mar 25, 2025 •

edited by kibanamachine

Loading

Uh oh!

tsullivan Mar 27, 2025

Uh oh!

Uh oh!

tomsonpl left a comment •

edited

Loading

Uh oh!

elasticmachine commented Apr 2, 2025

API count

async chunk count

Uh oh!

semd left a comment

Uh oh!

Uh oh!

kibanamachine commented Apr 3, 2025

Uh oh!

kibanamachine commented Apr 3, 2025

Uh oh!

tsullivan commented Apr 4, 2025

Uh oh!

kibanamachine commented Apr 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

Conversation

tsullivan commented Mar 25, 2025 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots

Checklist

Uh oh!

tsullivan Mar 27, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

tomsonpl left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Apr 2, 2025

💚 Build Succeeded

Metrics [docs]

Module Count

Public APIs missing comments

Async chunks

Public APIs missing exports

Page load bundle

API count

async chunk count

History

Uh oh!

semd left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Apr 3, 2025

Uh oh!

kibanamachine commented Apr 3, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

tsullivan commented Apr 4, 2025

💚 All backports created successfully

Questions ?

Uh oh!

kibanamachine commented Apr 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

tsullivan commented Mar 25, 2025 •

edited by kibanamachine

Loading

tomsonpl left a comment •

edited

Loading