You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/05/19 22:13:12 UTC
[jira] [Comment Edited] (KAFKA-3732) Add an auto accept option to
kafka-acls.sh
[ https://issues.apache.org/jira/browse/KAFKA-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292243#comment-15292243 ]
Ismael Juma edited comment on KAFKA-3732 at 5/19/16 10:12 PM:
--------------------------------------------------------------
There are a number of distributions that alias `rm` to be interactive by default so there is definitely Linux precedent for prompting on dangerous operations. The typical switch to disable the prompts is `--force` (not super-descriptive though).
`TopicCommand` doesn't prompt on delete, but it does prompt when `max.message.bytes` is greater than the broker's default `max.message.bytes` (and if there's more than 1 replica). We have a `--force` switch to disable the prompt for that case.
was (Author: ijuma):
There are a number of distributions that alias `rm` to be interactive by default (`-i`) so there is definitely Linux precedent for prompting on dangerous operations. The typical switch to disable the prompts is `--force` (not super-descriptive though).
`TopicCommand` doesn't prompt on delete, but it does prompt when `max.message.bytes` is greater than the broker's default `max.message.bytes` (and if there's more than 1 replica). We have a `--force` switch to disable the prompt for that case.
> Add an auto accept option to kafka-acls.sh
> ------------------------------------------
>
> Key: KAFKA-3732
> URL: https://issues.apache.org/jira/browse/KAFKA-3732
> Project: Kafka
> Issue Type: Improvement
> Components: admin
> Affects Versions: 0.10.0.0
> Reporter: Mickael Maison
> Priority: Minor
>
> When removing ACLs, kafka-acls.sh always prompts the user to confirm the ACL change. Having an option to auto accept would make it easier to use kafka-acls.sh in scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)