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

ASF GitHub Bot commented on KAFKA-5830:
---------------------------------------

GitHub user mimaison opened a pull request:

    https://github.com/apache/kafka/pull/3785

    KAFKA-5830: kafka-configs.sh should allow deletion of all configs for…

    … an entity
    
    Added a --delete-all-configs flag to delete all configurations for a given 
entity

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mimaison/kafka KAFKA-5830

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3785.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3785
    
----
commit bba8715f97bdd152c30f9786b375fe52583995f6
Author: Mickael Maison <mickael.mai...@gmail.com>
Date:   2017-09-03T17:33:20Z

    KAFKA-5830: kafka-configs.sh should allow deletion of all configs for an 
entity
    
    Added a --delete-all-configs flag to delete all configurations for a given 
entity

----


> kafka-configs.sh should allow deletion of all configs for an entity
> -------------------------------------------------------------------
>
>                 Key: KAFKA-5830
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5830
>             Project: Kafka
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Mickael Maison
>            Assignee: Mickael Maison
>
> kafka-configs.sh only allows to delete specific configurations and actually 
> fails if one of the configuration provided does not exist. That makes it hard 
> to use and forces us to first query the details and parse the output in order 
> to know the configurations to delete.
> Having an option to delete all configuration for an entity would make it 
> easier to use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to