We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
customGroups
Describe the bug
When you change the ConfigMap jwt-to-rbac at the level of customGroups at runtime, this changes doesn't applied.
jwt-to-rbac
This is because this conditions will be always nil because ClusterRole or ClusterRoleBinding already exists.
nil
ClusterRole
ClusterRoleBinding
jwt-to-rbac/pkg/rbachandler/rbac_handler.go
Lines 248 to 250 in bb2185d
Lines 331 to 333 in bb2185d
Steps to reproduce the issue: Change something at customGroups level
Expected behavior
When someone change something at customGroups the ClusterRole & ClusterRoleBinding changes should be reflected
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
When you change the ConfigMap
jwt-to-rbac
at the level ofcustomGroups
at runtime, this changes doesn't applied.This is because this conditions will be always
nil
becauseClusterRole
orClusterRoleBinding
already exists.jwt-to-rbac/pkg/rbachandler/rbac_handler.go
Lines 248 to 250 in bb2185d
jwt-to-rbac/pkg/rbachandler/rbac_handler.go
Lines 331 to 333 in bb2185d
Steps to reproduce the issue:
Change something at
customGroups
levelExpected behavior
When someone change something at
customGroups
the ClusterRole & ClusterRoleBinding changes should be reflectedThe text was updated successfully, but these errors were encountered: