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
Extensions support a large set of functionality today, and will support even additional features in the future. What are the kinds of controls that Administrators of OpenSearch clusters can have, and how are they distinguished from one another?
Proposal
All Application Scopes should be human readable and a laymen can easily guess the features/functionality that is controlled by allowing / disallowing a scope. Scopes are separated into a top level namespace, then the feature area and latently an action, consider ?core.index:read?.
The text was updated successfully, but these errors were encountered:
Background
Administrators need mechanism to control what extensions can do through Applications Scopes.
Problem statement
Extensions support a large set of functionality today, and will support even additional features in the future. What are the kinds of controls that Administrators of OpenSearch clusters can have, and how are they distinguished from one another?
Proposal
All Application Scopes should be human readable and a laymen can easily guess the features/functionality that is controlled by allowing / disallowing a scope. Scopes are separated into a top level namespace, then the feature area and latently an action, consider
?core.index:read?
.The text was updated successfully, but these errors were encountered: