ramackri opened a new pull request, #1021:
URL: https://github.com/apache/ranger/pull/1021

   ## Summary
   
   Completes [RANGER-5647 / #1018](https://github.com/apache/ranger/pull/1018) 
for **ISO-format** tag expiry dates in policy-engine tests.
   
   PR #1018 changed slash-format fixture dates (`2026/06/15` → `2099/12/31`) in 
shared tag JSON files and `RangerPathResourceMatcher` thread safety. Two 
**inline ISO** `EXPIRES_ON` values in `test_policyengine_tag_hive.json` were 
left unchanged.
   
   After **2026-06-15**, CI `build-17` fails:
   
   ```
   TestPolicyEngine.testPolicyEngine_hiveForTag
   ALLOW 'select ssn from employee.personal;' for user1 using EXPIRES_ON tag
   ==> expected: <true> but was: <false>
   ```
   
   Tag policy uses `ctx.isAccessedAfter('expiry_date')`; once the clock passes 
the fixture expiry, access is denied.
   
   ## Changes
   
   | File | Change |
   |------|--------|
   | 
`agents-common/src/test/resources/policyengine/test_policyengine_tag_hive.json` 
| `2026-06-15T15:05:15.000Z` → `2099-12-31T15:05:15.000Z` for EXPIRES_ON 
**DESCENDANT** and **SELF** test cases |
   
   No policy-engine logic changes — test fixture dates only.
   
   ## Related
   
   - [#1018](https://github.com/apache/ranger/pull/1018) / 
[38d2153](https://github.com/apache/ranger/commit/38d21532259a9d19f9539ee358ec5b4c732f42ee)
 — slash-format dates + path matcher fix
   - Unblocks CI failures seen on unrelated PRs (e.g. #1020) that inherit the 
expired ISO dates
   
   ## Test plan
   
   - [ ] `mvn test -pl agents-common 
-Dtest=TestPolicyEngine#testPolicyEngine_hiveForTag,TestPolicyEngine#testPolicyEngine_hiveForTag_filebased
 -Drat.skip=true -Dcheckstyle.skip=true -Dpmd.skip=true -Dspotbugs.skip=true`
   


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

Reply via email to