vyommani commented on PR #1309: URL: https://github.com/apache/ranger/pull/1309#issuecomment-6208491888
> @vyommani - I suggest including changes to `RangerAccessResult` as well in this PR. It will provide complete integration details for services planning to leverage constraints. If any changes are expected in policy engine calls (`isAccessAllowed(request)`), hopefully not, consider including those details as well in this PR. Note that implementations can come later. Thanks Madhan. The RangerAccessResult changes are in RANGER-5842, stacked on this PR. There’s no change to isAccessAllowed(request). When access is allowed, the result includes getConstraintResults(), which the service enforces; on deny it’s empty. I’d prefer to review that API together with its implementation, but I’m happy to move it here if you’d rather. -- 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]
