| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Images are ready for the commit at 569f2ba. To use with deploy scripts, first export MAIN_IMAGE_TAG=4.1.x-340-g569f2ba014. |
Sorry, something went wrong.
|
Images are ready for the commit at 42ab190. To use with deploy scripts, first export MAIN_IMAGE_TAG=4.1.x-277-g42ab1905ad. |
Sorry, something went wrong.
|
/retest |
Sorry, something went wrong.
|
|
||
| var sacQueryFilter *v1.Query | ||
| if s.hasPermissionsChecker() { | ||
| if ok, err := s.permissionChecker.GetAllowed(ctx); err != nil || !ok { |
There was a problem hiding this comment.
In the current state of existing PermissionChecker implementation, it does not make any difference, as these will check for global read access to the underlying resource(s).
Nevertheless, the generated store code was calling GetManyAllowed on the permission checker.
Sorry, something went wrong.
|
/retest |
Sorry, something went wrong.
|
Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready. |
Sorry, something went wrong.
|
@janisz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist
If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.