You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Dineshkumar Yadav (Jira)" <ji...@apache.org> on 2020/11/11 12:15:00 UTC

[jira] [Issue Comment Deleted] (RANGER-3078) Supporting import policy based on PolicyName, ServiceName and ZoneName

     [ https://issues.apache.org/jira/browse/RANGER-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dineshkumar Yadav updated RANGER-3078:
--------------------------------------
    Comment: was deleted

(was: [commit : 8d3ef6f8c9bf017f90d8edf52648ce2b04d0cbe6|https://github.com/apache/ranger/commit/8d3ef6f8c9bf017f90d8edf52648ce2b04d0cbe6])

> Supporting import policy based on PolicyName, ServiceName and ZoneName
> ----------------------------------------------------------------------
>
>                 Key: RANGER-3078
>                 URL: https://issues.apache.org/jira/browse/RANGER-3078
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Dineshkumar Yadav
>            Assignee: Dineshkumar Yadav
>            Priority: Major
>
> Currently we support Import Policy by matching the resource signature of existing policy .  
> Now we support below matching criteria 
> 1. matching by resource signature
> 2. matching by policy Name, Service Name and Zone Name
> A. By default it will use matching by resource signature. 
> B. If you want to match by PolicyName then you have to pass extra parameter "policyMatchingAlgorithm=matchByName" while calling import API.
> C. if you want to specify match by resource signature then you can pass "policyMatchingAlgorithm=matchByPolicySignature" while calling import API.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)