sungwy commented on code in PR #3760: URL: https://github.com/apache/polaris/pull/3760#discussion_r2819912584
########## polaris-core/src/main/java/org/apache/polaris/core/auth/AuthorizationState.java: ########## @@ -0,0 +1,38 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ +package org.apache.polaris.core.auth; + +import jakarta.annotation.Nonnull; +import org.apache.polaris.core.persistence.resolver.PolarisResolutionManifest; + +/** + * Request-scoped authorization state shared across authorization phases. + * + * <p>Distinct from {@link org.apache.polaris.core.context.CallContext}. This state is intended to + * carry authorization-specific data, such as a {@link PolarisResolutionManifest} created by the + * caller and populated by the authorizer. + */ +public interface AuthorizationState { Review Comment: I did this intentionally because I wanted to keep `AuthorizationState` in `polaris-core` and the request-scoped CDI in `polaris-runtime`. But yes, I agree that we would not intend for there to be multiple implementations -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
