You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: pkg/authorization/authorizer/attributes_test.go
+7-7
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ import (
7
7
)
8
8
9
9
funcTestAuthorizationAttributes(t*testing.T) {
10
-
// Wrapper to make sure additions to the AuthorizationAttributes interface get corresponding fields added in api.AuthorizationAttributes
11
-
// If an additional function is required to satisfy this interface, the data for it should come from the contained authorizationapi.AuthorizationAttributes
@@ -129,7 +129,7 @@ func (a *openshiftAuthorizer) getAllowedSubjectsFromNamespaceBindings(ctx kapi.C
129
129
// authorizeWithNamespaceRules returns isAllowed, reason, and error. If an error is returned, isAllowed and reason are still valid. This seems strange
130
130
// but errors are not always fatal to the authorization process. It is entirely possible to get an error and be able to continue determine authorization
131
131
// status in spite of it. This is most common when a bound role is missing, but enough roles are still present and bound to authorize the request.
0 commit comments