rocketmq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [rocketmq] yuz10 opened a new issue #3281: cannot delete topic/group perms in acl config
Date Fri, 20 Aug 2021 14:54:32 GMT

yuz10 opened a new issue #3281:
URL: https://github.com/apache/rocketmq/issues/3281


   The issue tracker is **ONLY** used for bug report(feature request need to follow [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)).
Keep in mind, please check whether there is an existing same report before your raise a new
one.
   
   Alternately (especially if your communication is not a bug report), you can send mail to
our [mailing lists](http://rocketmq.apache.org/about/contact/). We welcome any friendly suggestions,
bug fixes, collaboration and other improvements.
   
   Please ensure that your bug report is clear and that it is complete. Otherwise, we may
be unable to understand it or to reproduce it, either of which would prevent us from fixing
the bug. We strongly recommend the report(bug report or feature request) could include some
hints as the following:
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   
   In `mqadmin updateAclConfig -n localhost:9876 -a abcdefg -s abcdefg -c RaftCluster -g groupa=SUB`
   sets group groupPerms to `groupa=SUB`
   and then wants to delete groupPerms using
    `mqadmin updateAclConfig -n localhost:9876 -a abcdefg -s abcdefg -c RaftCluster -g ""`
   
   - What did you expect to see?
   groupPerms is empty
   
   - What did you see instead?
   cannot delete groupPerms, its still `groupa=SUB`
   
   2. Please tell us about your environment:
   
   3. Other information (e.g. detailed explanation, logs, related issues, suggestions how
to fix, etc):
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have).
Are you currently using any workarounds to address this issue?
   
   4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue
to map to the sub task:
   
   - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, 
   - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
   - ...
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



Mime
View raw message