[Fleet][GS] Add Fleet deep links to navigational search

[joshdover]

Currently blocked by #96134

Meta issue: #72680

In #83380 we added support for applications to include a searchDeepLinks property on their core.application.register call which feeds into the navigational search feature.

Fleet should add this property to add deep links for their key locations to search. In most cases, this should be adding an array with the name of the location and a URL path to the route in your app. See the documentation for this API for more info. Some things to consider:

• The title for each link should be localized
• The path for each link should be relative to your application's appRoute. Base path does not need to be included.
• If there are locations that are only conditionally available (for example, due to licensing or feature controls), you can utilize the appUpdater$ API. See the example in the Stack Management app.

New links to add

Fleet

• Overview (same entry point as Fleet app)
• Integrations
• Including all available integrations
• Configurations
• Fleet
• Datasets
• Add agent

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[elasticmachine]

Pinging @elastic/ingest-management (Feature:Fleet)

[jfsiii]

I think we can add/export a new data structure in
https://github.com/elastic/kibana/blob/d18fca3b8265bc2276800aec9b322f378abfeadb/x-pack/plugins/fleet/public/applications/fleet/constants/page_paths.ts that gets the path value from the existing variables like

kibana/x-pack/plugins/fleet/public/applications/fleet/constants/page_paths.ts

Line 46 in d18fca3

policies: '/policies',

[joshdover]

@jfsiii @jen-huang Is this something that will make 7.12? I imagine it's not a whole lot of work based off the suggestion above.

[jfsiii]

@joshdover I think you're right that it's not a lot of work, but cc @ph because I don't believe we have assigned this to a release.

[jen-huang]

@jloleysens I found this old issue that would be closed by your PR #102227 :) The AC here talks about the subpages too, but now that Integrations is separated out, I'm comfortable with just Integrations + Fleet present in the search results.

[dikshachauhan-qasource]

Hi @jloleysens

While performing testing on #102227 feature merges, we have come up with following queries:

• Could you please confirm how a package is defined. Like Apache is accepted as package while Windows and other few integrations are not at global search bar with type:package filter.
• What are the expected inputs to hit search as a package. Aren't all integrations are eligible to be searched under it.

For now we have reported issue: #104411

Thanks
QAS

[jloleysens]

I'll respond on the open issue