-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RBAC - Schema registry subjects bindings are never deleted #513
Comments
Hi @damien-malescot, I have done in #516 some validation of possible problems with the delete of subjects, sadly I'm not able to reproduce it yet. As you can see there, subjects gone, gone in my test. Is anything specific you might have in your config file? |
Hi, I'm on holidays, i will check that in 3 weeks. Thanks |
Hi @purbon , indeed it works with the master version. Just to let you know, we have added a subject management prefix filter in our fork. We would like to use the official version or at least something really similar in order to reduce our maintenance work. that's why we are creating all these issues in order to improve Julie. |
@ludovic-boutros, feel free to push a PR if that is ok for you! I'm very open to that kind of contribution! and I think that would help the project a lot. Thanks a lot for all your efforts and help! it is honestly much appreciated. |
Hello @purbon, after some research with @damien-malescot , it seems that it is due to this parameter One question, did you already try using random parameters for some tests or parametrized tests (Junit5) in order to tests a lot of parameter combinations ? (#534) |
Describe the bug
When we remove subjects from a topoligy, bindings are not removed from RBAC
To Reproduce
Create a topology file like this :
Bindings are created :
Remove all from topology and apply :
Subject's bindings is still present :
Expected behavior
Subjects's bindings must be removed when they are deleted from topology files.
You should use a property like for topics to recognize managed subjects :
topology.subject.managed.prefixes";
The text was updated successfully, but these errors were encountered: