Repository navigation
13647 fixed wrong feature flag for checking admin fine-grained authz - #13648
Conversation
|
Here is the PR for fixing other wrong usages of the profile flag. |
|
@sschu Thanks. Looks like some tests are failing because now the |
|
I'll have a look. |
24a9e8d to
a9382b7
Compare
|
@pedroigor I had to adapt some tests to also enable the profile feature correctly. I hope that does the trick. |
|
@sschu Thanks again! Makes more sense for me too. However, I'm afraid we still have some null checks to make like:
The only reason why they don't fail is because of checks like So the places still using the I would say we can leave those as is and merge the PR. But if you think you have a better idea to improve the code, please let me know. |
|
@pedroigor The general idea is to only check for the profile feature in one place in 'MgmtPermissions' and use I also added some source code comments/questions, feel free to respond to them. If you like the changes I would finalise the second commit and finally squash it before merging. |
536f673 to
042b5d7
Compare
There was a problem hiding this comment.
I don't think it does. The calling code does not call this method if the feature is disabled. See
.There was a problem hiding this comment.
Same comment and code pattern from the previous comments on clients.
There was a problem hiding this comment.
Same comment and code pattern from the previous comments on clients.
There was a problem hiding this comment.
I don't think so. We can do the same as others and see how it goes.
There was a problem hiding this comment.
Same comment and code pattern from the previous comments on clients.
There was a problem hiding this comment.
Definitely :) Let's remove it.
There was a problem hiding this comment.
Same comment and code pattern from the previous comments on clients.
|
@sschu I'm really pleased to collaborate with you on these changes and your willingness to improve this area. Thanks a lot for your time and effort. Despite the answers to some of your comments, the proposed changes LGTM and they should help us to create a baseline to perform more aggressive refactoring in the future. |
042b5d7 to
b0f086d
Compare
|
@pedroigor Thanks for the roses! ;) I am also happy to contribute. I implemented your suggestions. Should I then squash the commits if everything is fine or can it be automatically squash-merged? |
|
I can squash before merging. |
|
Hmm, the failing test ran fine locally. |
…Will be squashed later if accepted.
b0f086d to
11f5ec6
Compare
|
@pedroigor The test failure is most likely not related to my changes. |
Fixes #13647.