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
Is your feature request related to a problem? Please describe.
As documented, using index management features is only supported when caller is a member of the all_access role:
To use the ISM plugin, your user role needs to be mapped to the all_access role that gives you full access to the cluster. To learn more, see Users and roles.
This means that it is not possible to delegate index management API calls to partner systems without giving them full cluster management access .
Describe the solution you'd like
The API calls for creating/updating/deleting an ISM policy should be a separate permission which is assignable to a custom role.
…pensearch-project#50)
* Added PolicySettings and DeleteModal components for View Policy UI
* Added PolicySettings test snapshot and fixed placeholder edit button
* Fixing DeleteModal renders component test
* Fixed interface duplication, cleaned up PolicySettings, fixed PolicySettings test
* Simplified ISMTemplate handling, removed unnecessary coversion function
* Added ISM Template count to panel title
* Fixing timezone dependency on PolicySettings test
Signed-off-by: Eric Lobdell <lobdelle@amazon.com>
Tuesday Nov 24, 2020 at 09:46 GMT
Originally opened as opendistro-for-elasticsearch/index-management#351
Is your feature request related to a problem? Please describe.
As documented, using index management features is only supported when caller is a member of the
all_access
role:This means that it is not possible to delegate index management API calls to partner systems without giving them full cluster management access .
Describe the solution you'd like
The API calls for creating/updating/deleting an ISM policy should be a separate permission which is assignable to a custom role.
e.g.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: