You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
In my understanding the
Epinova.ElasticSearch.Core.Admin.Index.EnableClosing
method will throw an exception if user not havingcluster:manage
privileges.Could
cluster:manage
privileges be configured, asopt-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 withclosing enabled
, this code would not be necessary to run? All other cluster-methods seems to work withcluster:monitor
privileges. Then I guess anopt-out
would be good here? This is the only place wherecluster: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.
The text was updated successfully, but these errors were encountered: