You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2023/02/22 15:42:00 UTC

[jira] [Comment Edited] (IGNITE-18819) Permissions for cluster activation/deactivation.

    [ https://issues.apache.org/jira/browse/IGNITE-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691480#comment-17691480 ] 

Vladimir Steshin edited comment on IGNITE-18819 at 2/22/23 3:41 PM:
--------------------------------------------------------------------

ADMIN_OPS is already checked to chenge cluster state from remote control like control.sh or REST API. MIght be used like ADMIN_SNAPSHOT for all the shanpshot operations.


was (Author: vladsz83):
ADMIN_OPS is already checked to chenge cluster state from remote control like control.sh or REST API. Should be used like ADMIN_SNAPSHOT for all the shanpshot operations.

> Permissions for cluster activation/deactivation.
> ------------------------------------------------
>
>                 Key: IGNITE-18819
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18819
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Assignee: Vladimir Steshin
>            Priority: Major
>              Labels: ise
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Cluster activation/deactivation actions should have permission like JOIN_AS_SERVER, ADMIN_SNAPSHOT or existing ADMIN_OPS.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)