ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (RANGER-3078) Supporting import policy based on PolicyName, ServiceName and ZoneName
Date Thu, 12 Nov 2020 20:41:00 GMT

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

Abhay Kulkarni resolved RANGER-3078.
------------------------------------
    Resolution: Fixed

Commit details:

master:

https://github.com/apache/ranger/commit/208b6df0d42d63eb5834c889afb092b7a69146a4

 

ranger-2.2:

https://github.com/apache/ranger/commit/a9e637cf8289e8de5f440b5e7a526aafd573aa0a

> 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)

Mime
View raw message