In my understanding the Epinova.ElasticSearch.Core.Admin.Index.EnableClosing method will throw an exception if user not having cluster:manage privileges.
Could cluster:manage privileges be configured, as opt-out, so this code won't run and throw an exception in initialization?
I mean, if the user has the cluster:monitor privileges, and the cluster is already configured with closing enabled, this code would not be necessary to run? All other cluster-methods seems to work with cluster:monitor privileges. Then I guess an opt-out would be good here? This is the only place where cluster:manage privileges is used, right?
We will be running our indices in a cluster among other indices, and therefore have demands/requests of our user not being granted with too much privileges.
In my understanding the
Epinova.ElasticSearch.Core.Admin.Index.EnableClosingmethod will throw an exception if user not havingcluster:manageprivileges.Could
cluster:manageprivileges be configured, asopt-out, so this code won't run and throw an exception in initialization?I mean, if the user has the
cluster:monitorprivileges, and the cluster is already configured withclosing enabled, this code would not be necessary to run? All other cluster-methods seems to work withcluster:monitorprivileges. Then I guess anopt-outwould be good here? This is the only place wherecluster:manageprivileges is used, right?We will be running our indices in a cluster among other indices, and therefore have demands/requests of our user not being granted with too much privileges.