You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (JIRA)" <ji...@apache.org> on 2019/05/01 18:16:00 UTC
[jira] [Updated] (RANGER-2412) Policy Condition Evaluators existing
and newly created should work in both policy level and policy item level
[ https://issues.apache.org/jira/browse/RANGER-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Mani updated RANGER-2412:
--------------------------------
Description:
Policy Condition Evaluators existing and newly created should work in both policy level and policy item level.
With the introduction of Policy Level condition in https://issues.apache.org/jira/browse/RANGER-2354, now can set policy conditions at Policy level also. But this needs a new variable "policyCondition" to be referred if some one wants to created a new policy level condition evaluator (https://cwiki.apache.org/confluence/display/RANGER/Dynamic+Policy+Hooks+in+Ranger+-+Configure+and+Use) . Existing policy level condition also needs to be duplicated to have this new "policyCondition" to be referred. Instead on this its good to use the same "condition" variable. This will allow anyone to use the existing policy condition evaluator to be used in policy level or policy item level. Same is the case with newly created custom policy condition evaluators
was:
Policy Condition Evaluators existing and newly created should work in both policy level and policy item level.
With the introduction of Policy Leven condition in https://issues.apache.org/jira/browse/RANGER-2354, now can set policy conditions at Policy level also. But this needs a new variable "policyCondition" to be referred if some one wants to created a new policy level condition evaluator (https://cwiki.apache.org/confluence/display/RANGER/Dynamic+Policy+Hooks+in+Ranger+-+Configure+and+Use) . Existing policy level condition also needs to be duplicated to have this new "policyCondition" to be referred. Instead on this its good to use the same "condition" variable. This will allow anyone to use the existing policy condition evaluator to be used in policy level or policy item level. Same is the case with newly created custom policy condition evaluators
> Policy Condition Evaluators existing and newly created should work in both policy level and policy item level
> -------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-2412
> URL: https://issues.apache.org/jira/browse/RANGER-2412
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.0.0
> Reporter: Ramesh Mani
> Assignee: Ramesh Mani
> Priority: Major
> Fix For: 2.0.0
>
>
> Policy Condition Evaluators existing and newly created should work in both policy level and policy item level.
> With the introduction of Policy Level condition in https://issues.apache.org/jira/browse/RANGER-2354, now can set policy conditions at Policy level also. But this needs a new variable "policyCondition" to be referred if some one wants to created a new policy level condition evaluator (https://cwiki.apache.org/confluence/display/RANGER/Dynamic+Policy+Hooks+in+Ranger+-+Configure+and+Use) . Existing policy level condition also needs to be duplicated to have this new "policyCondition" to be referred. Instead on this its good to use the same "condition" variable. This will allow anyone to use the existing policy condition evaluator to be used in policy level or policy item level. Same is the case with newly created custom policy condition evaluators
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)