[Security Solution] Remove classic stateful navigation #179572
Labels
Comments
|
Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore) |
semd
added a commit
that referenced
this issue
Apr 12, 2024
## Summary issue: #179162 This PR brings the new navigation, with the solution-centric IA (Information Architecture), to the ESS (stateful) Security Solution. To do so, the implementation of the `navigationTree$`, which was previously only implemented in serverless, has been integrated inside the generic "security_solution" plugin, so now it is available for ESS and serverless offerings. In ESS users can still choose the navigation version, so we have to temporarily keep supporting both, the classic and new navigation implementations. After the rollout, the classic navigation components will be removed and the unified links architecture should be reassessed. The issue for the cleaning: #179572 ### Rollout The new solutions navigation will not be available for customers on 8.14, it will only be enabled for internal Elastic users (via Lauchdarkly), who will have the ability to opt out of it from their profile menu. We'll collect feedback and telemetry and address any bugs or improvements (together with the Kibana platform team). The plan is to start making it available to customers in 8.15. ### Testing Unless we add the _kibana.yml_ configurations to enable the new navigation, the regular classic navigation will be displayed, it should keep working the same way without any change. The new landing pages (`Assets`, `Investigations`, `Machine Learning`,...), that exist only when using the new navigation, should not be accessible using the classic version. To enable the new navigation add the following _kibana.yml_ configs: ``` xpack.cloud_integrations.experiments.enabled: true xpack.cloud_integrations.experiments.flag_overrides: "navigation.solutionNavEnabled": true xpack.cloud.id: "ftr_fake_cloud_id:aGVsbG8uY29tOjQ0MyRFUzEyM2FiYyRrYm4xMjNhYmM=" xpack.cloud.base_url: "https://cloud.elastic.co" xpack.cloud.deployment_url: "/deployments/deploymentId" ``` And enable the advanced setting  ### Screenshots The app switcher: <img width="293" alt="app switcher" src="https://github.com/elastic/kibana/assets/17747913/0a638b8f-fdc0-4d1a-b8d3-607e487215f4"> --- New Assets landing page: <img width="549" alt="assets landing" src="https://github.com/elastic/kibana/assets/17747913/17bc8a94-02b4-4996-b9f5-8731ba81ac43"> --- For `Stack Management` we set the nav panel flyout and the cards landing page, this is temporary until a decision on how to show Stack Management links is made: <img width="954" alt="stack management" src="https://github.com/elastic/kibana/assets/17747913/27ce6534-0508-4804-b224-8dc409042825"> --- The switch to go back to the classic nav is in the profile menu at the top-right corner:  --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> Co-authored-by: Katerina <aikaterini.patticha@elastic.co> Co-authored-by: Sébastien Loix <sebastien.loix@elastic.co> Co-authored-by: Kurt <kc13greiner@users.noreply.github.com> Co-authored-by: Justin Kambic <jk@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
related to: #179162
Remove the classic navigation after the "solution" navigation rollout in ess is over.
This may include:
The text was updated successfully, but these errors were encountered: