You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2022/07/21 19:39:00 UTC
[jira] [Commented] (CASSANDRA-17767) Add guardrail to disallow DROP KEYSPACE commands for non superuser accounts
[ https://issues.apache.org/jira/browse/CASSANDRA-17767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569671#comment-17569671 ]
Josh McKenzie commented on CASSANDRA-17767:
-------------------------------------------
||Item|Link||
||PR|[Link|https://github.com/apache/cassandra/pull/1740]|
||JDK8 CI|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/242/workflows/456fdc77-c2e7-4e2c-92db-a73adef9cc92]|
||JDK11 CI|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/242/workflows/a767f637-3d3a-4080-be26-74ad5c14184f]|
> Add guardrail to disallow DROP KEYSPACE commands for non superuser accounts
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-17767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17767
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> Similar to CASSANDRA-17558, we should have the ability to ban DROP KEYSPACE commands cluster-wide for non superuser accounts.
> The goal as with blocking DROP/TRUNCATE TABLE is to help prevent users from inadvertently throwing away data and providing a cleaner way for operators to just disable this cluster-wide than role management / runbook / etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org