[Index Management] Add indices list columns to the extensions service

[yuliacech]

Summary

This PR adds a function to the extensions service that allows to add new columns to the indices list. The new column can display information that is already available in the index data or a new index data enricher can be registered. See readme for more details.

Screenshot

Example of adding an ILM phase column
86864fe

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[yuliacech]

/ci

[yuliacech]

/ci

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[TattdCodeMonkey]

TIL, this is great. We should be using this for serverless search.

[TattdCodeMonkey]

Not needed now, but in the future we may want to allow the columnConfig to optionally override this eui-textLeft class. I'm not sure how often designers would want different alignments for cell content, but in the past I've had to do right alignment for columns with numbers.

[yuliacech]

Yes, we had some numbers columns right aligned as well. We can add to the column config in the future when needed.

[ElenaStoeva]

Thanks for working on this @yuliacech! Tested locally adding a column and it worked fine. However, I noticed that clicking the column header doesn't seem to sort the rows properly:

Screen.Recording.2024-01-18.at.16.35.33.mov

Here is how I added the column:

  extensionsService.addColumn({
    label: 'ILM phase',
    fieldName: 'ilm.phase',
    order: 90,
    render: (index: Index) => (index.ilm?.managed ? index.ilm.phase : 'test'),
  });

Would that be possible to be fixed somehow?

[yuliacech]

That's right, the sorting doesn't work with the extended columns yet, I'll open an issue for that, thanks for the review @ElenaStoeva!

[yuliacech]

Opened #175140 to track the sorting issue @ElenaStoeva
cc @TattdCodeMonkey this could affect the "ingestion method" column as well

[ElenaStoeva]

That's right, the sorting doesn't work with the extended columns yet, I'll open an issue for that, thanks for the review @ElenaStoeva!

Thanks for clarifying @yuliacech, changes LGTM!

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 4404c85

Failed CI Steps

• FTR Configs #24

Test Failures

• [job] [logs] FTR Configs #24 / X-Pack Accessibility Tests - Group 1 Dashboard links a11y tests "after all" hook for "Links panel"
• [job] [logs] FTR Configs #24 / X-Pack Accessibility Tests - Group 1 Dashboard links a11y tests Non-empty links editor flyout

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
indexManagement	586.7KB	587.0KB	+357.0B

Page load bundle

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

id	before	after	diff
indexManagement	35.0KB	35.2KB	+130.0B

History

• 💚 Build #188255 succeeded 029cf8d
• 💚 Build #187537 succeeded f3f3d18
• 💔 Build #187281 failed db6cbe6

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