[FEATURE] Use index templates for `tenant_template`

[AMoo-Miki]

Is your feature request related to a problem?

security-dashboards-plugin/server/multitenancy/tenant_index.ts

Lines 41 to 62 in 3abb707

	await esClient.indices.putTemplate({
	name: 'tenant_template',
	body: {
	index_patterns: [
	opensearchDashboardsIndex + '_-*_*',
	opensearchDashboardsIndex + '_0*_*',
	opensearchDashboardsIndex + '_1*_*',
	opensearchDashboardsIndex + '_2*_*',
	opensearchDashboardsIndex + '_3*_*',
	opensearchDashboardsIndex + '_4*_*',
	opensearchDashboardsIndex + '_5*_*',
	opensearchDashboardsIndex + '_6*_*',
	opensearchDashboardsIndex + '_7*_*',
	opensearchDashboardsIndex + '_8*_*',
	opensearchDashboardsIndex + '_9*_*',
	],
	settings: {
	number_of_shards: 1,
	},
	mappings,
	},
	});

Since the legacy template currently being used can be overridden by index templates, it would be better to have tenant_template created as an index template and with the highest possible priority to protect all .kibana* system indices from being corrupted simply because their mapping was overridden by some overzealous index template.

What solution would you like?
Use client.indices.putIndexTemplate and set priority to perhaps 2⁶³-1.

What alternatives have you considered?
None

Do you have any additional context?
No

[cliu123]

@AMoo-Miki Thanks for filing the issue! I'm changing priority to order.
But if the order is set to 2⁶³-1 would disallow users to override the the tenant-template. Would something like 99 fit this case better? Then users would be able to override tenant-template by explicitly setting custom index templates to something > 99.

[AMoo-Miki]

@cliu123 AFAIK, index templates don't use order and use priority; the legacy templates used order.

Why would this plugin want to allow overriding its mapping or configuration? Even a tiny bit of change to this template would break the functionality of Dashboards.

[cliu123]

@AMoo-Miki You're right. order is only for the lagacy template.