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

   ## Summary
   
   - Adds `ranger-audit-dest-auditserver` (`RangerAuditServerDestination`) so 
plugins post access audits to the PR-1 ingestor instead of bundling Solr/HDFS 
dest jars by default.
   - Wires plugin/agent POMs, `*-audit-changes.cfg`, install properties, and 
distro assemblies to `ranger-audit-dest-auditserver`.
   - `agents-common`: `jersey-bundle` dependency fix; Nashorn reflection for 
modular JDK; `enable-agent.sh` yarn lib path fix.
   - Knox/KMS: Jersey/jsr311 packaging adjustments for audit-server REST client.
   
   ## Pipeline context
   
   ```
   Plugins ──► dest-auditserver ──► audit-ingestor (PR-1) ──► Kafka ──► 
dispatchers ──► OpenSearch
            (this PR)
   Admin UI reads OpenSearch (PR-2, parallel)
   Docker/CI E2E (PR-4, after this PR)
   ```
   
   Depends on **PR-1** (#1243) merged into `ranger-2.10`. Independent of PR-2 
admin UI.
   
   ## Intentionally excluded (vs full backport branch)
   
   | Excluded | Reason |
   |----------|--------|
   | Root `pom.xml` protobuf/ORC/GCP downgrades | Would revert RANGER-5785 on 
`ranger-2.10` |
   | `RangerRESTClient.java` | Import-order only; no behavior change |
   | `RangerHiveAuthorizerBase.java` | Unrelated Hive ConfVars API change |
   | `kms.xml` wholesale re-indent | Kept 2.10 formatting; only audit dest 
include line changed |
   | SPIFFE / RANGER-5723 header auth | Out of 2.10 audit backport scope |
   
   ## Test plan
   
   - [ ] `mvn -pl agents-audit/dest-auditserver,agents-common -am verify 
-DskipTests` (JDK 8)
   - [ ] Build one plugin tarball (e.g. HDFS/KMS/Knox) and confirm 
`ranger-audit-dest-auditserver` in `lib/` / plugin-impl
   - [ ] With ingestor up (PR-1), enable 
`xasecure.audit.destination.auditserver` and confirm audits reach Kafka
   
   
   Made with [Cursor](https://cursor.com)


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