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

Aleksey Yeschenko commented on CASSANDRA-17558:
-----------------------------------------------

I'd prefer to change it now if we are changing it at all, yes.

> Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser 
> accounts
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17558
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17558
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Feature/Guardrails
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>             Fix For: 4.1
>
>
> While this can also be accomplished via roles, there's value in having a 
> cluster-wide "all role ban" on specific operations that operators can 
> configure for clusters that have need of those settings.
> In this case, we want the ability to completely disallow DROP or TRUNCATE 
> TABLE commands so users cannot inadvertently throw away data and operators 
> don't have to runbook managing roles to ensure that this functionality 
> doesn't leak through.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to