Currently Optimize modifies the cluster setting 'action.auto_create_index', as this is a concern of the one who operates the elasticsearch cluster and requires optimize to be granted the cluster:admin/settings/update we should remove that behavior.
If we want to ensure during testing that Optimize does not accidentally creates rouge indexes we should just ensure this setting is set to false in the context of our IT's.
- Optimize does not modify the 'action.auto_create_index' in production
- the cluster setting 'action.auto_create_index' is only set in the context of runnings IT's to ensure no rouge indexes are created (e.g. by ElasticsearchRule)