[Index Management] Add index mode field in index template form

[ElenaStoeva]

Closes #198620

Summary

This PR adds a field for index mode setting in the Logistics step in Index Template form.

Screen.Recording.2024-11-13.at.13.32.52.mov

How to test:

1. Go to Index Management -> Index Templates and start creating an index template
2. Verify that the index mode is only enabled if the data stream toggle is on.
3. Verify that typing the logs-*-* index pattern sets the index mode to "LogsDB":

4. Go to the Settings step and verify that the index mode callout is displayed correctly.
5. Go to Review step and verify that Index mode is displayed correctly in both the summary and the preview request.
6. Save the template and verify that the template details tab correctly displays the index mode.

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
• Unit or functional tests were updated or added to match the most common scenarios
• 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)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)

[mattkime]

Overall the code looks good and works well but I have a few questions. I'm not sure anything will change but I figure its at least worth a conversation.

I'm a bit confused by what the 'Create Data Stream' toggle does. I see that it corresponds to the ES api which leaves me similarly confused. I thought it might create a data stream but it doesn't seem to have done that. Or perhaps I did something wrong or I'm otherwise confused.

Is the callout about index.mode being set really needed? I could see displaying it if the user attempted to set the value but most of the time we're probably telling people not to do something they have no intention of doing. IMO it would be better to display it only if someone was trying to set it.

I noticed that the index settings mode will show the index.mode setting when an index template is edited but not on initial creation. Ideally the content would be the same.

[ElenaStoeva]

I'm a bit confused by what the 'Create Data Stream' toggle does. I see that it corresponds to the ES api which leaves me similarly confused. I thought it might create a data stream but it doesn't seem to have done that. Or perhaps I did something wrong or I'm otherwise confused.

My understanding of the docs is that if the data_stream object is included, this template can be used for creating data streams that match the index pattern of this index template.

Is the callout about index.mode being set really needed? I could see displaying it if the user attempted to set the value but most of the time we're probably telling people not to do something they have no intention of doing. IMO it would be better to display it only if someone was trying to set it.

That was a bit of a last-minute decision with the idea that we might update this depending on usage evaluations. cc: @bitzandeb

I noticed that the index settings mode will show the index.mode setting when an index template is edited but not on initial creation. Ideally the content would be the same.

Do you mean that the editor doesn't have the index mode setting prepopulated with the selected index mode field? If so, this is a bit too complex, given that there are different formats of inputting the settings (i.e. "index.mode" or "index": {"mode"...}) and we would need to parse and modify any existing input that the user has added. For the sake of merging the changes on time, we decided to only display the warning callout as we don't know how these interactions are going to play out.

[dmlemeshko]

x-pack/test_serverless/api_integration/services/index_management/svl_templates.helpers.ts changes LGTM

[kibanamachine]

Starting backport for target branches: 8.x

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 33e650f

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
indexManagement	695	696	+1

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
indexManagement	236	238	+2

Async chunks

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

id	before	after	diff
indexManagement	690.0KB	693.1KB	+3.1KB

Page load bundle

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

id	before	after	diff
indexManagement	46.1KB	46.3KB	+287.0B

Unknown metric groups

API count

id	before	after	diff
indexManagement	241	243	+2

History

• 💔 Build #251369 failed 8af1417
• 💔 Build #251320 failed 7816c2c
• 💔 Build #251240 failed 93316b0
• 💔 Build #250972 failed 6231852
• 💔 Build #250848 failed efa8406

cc @ElenaStoeva

[kibanamachine]

💚 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