Use doc link services in index management

[lcawl]

Summary

Related to #88107

This PR removes hard-coded links from x-pack/plugins/index_management/public/application/components/component_templates/lib/documentation.ts and x-pack/plugins/index_management/public/application/services/documentation.ts, replacing them with keywords from the documentation link service.

In the long run, these documentation.ts files should likely be removed and the doc link service called directly instead.

[lcawl]

@elasticmachine merge upstream

[kibanamachine]

merge conflict between base and head

[lcawl]

@elasticmachine merge upstream

[mattkime]

changes lgtm

[mattkime]

@elasticmachine merge upstream

[alisonelizabeth]

Thanks for working on this @lcawl! Index Management has a lot of doc links to cover 😄 .

In the long run, these documentation.ts files should likely be removed and the doc link service called directly instead.

I agree. I started looking into addressing this myself on your branch, but it will require touching a number of files and I think might be more appropriate to address as a separate PR. I can open up an issue to track this work.

I also noticed there are still a handful of hard-coded links generated using esDocsBath (it looks confined to the step_ components - step_aliases, step_settings, step_mappings). Should these be added to the core doc links service as well?

[lcawl]

@elasticmachine merge upstream

[kibanamachine]

merge conflict between base and head

[lcawl]

I also noticed there are still a handful of hard-coded links generated using esDocsBase (it looks confined to the step_ components - step_aliases, step_settings, step_mappings). Should these be added to the core doc links service as well?

Yes, good catch. I added keywords for those hard-coded links in the core doc link service, but haven't updated the TSX files to use them. It seems to me that would make sense to do after this app is using the core doc link service in general. If you disagree, let me know and I can add that to this PR.

[alisonelizabeth]

Latest LGTM. Thanks again for working on this @lcawl! I left one question about the doc link for the boost parameter. Would you mind taking a look before merging?

I also opened #96910 as a follow up to remove the documentation service.

[lcawl]

@elasticmachine update branch

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3cbe372
• Storybooks Preview

Metrics [docs]

Async chunks

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

id	before	after	diff
dataEnhanced	159.1KB	159.0KB	-171.0B
indexManagement	1.3MB	1.3MB	+3.8KB
total			+3.6KB

Page load bundle

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

id	before	after	diff
core	377.0KB	379.7KB	+2.7KB

History

• 💔 Build #119013 failed b59b68e
• 💔 Build #118965 failed 71a0da8
• 💔 Build #118960 failed ff98993
• 💔 Build #118838 failed 4764869
• 💚 Build #116611 succeeded abbc736

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream