ramackri opened a new pull request, #1045: URL: https://github.com/apache/ranger/pull/1045
## Summary Backport of [deaf13df3](https://github.com/apache/ranger/commit/deaf13df3c62af8edde53e185890682fb711bec5) / [#1037](https://github.com/apache/ranger/pull/1037) to `ranger-2.9`. Remove the legacy `atlas.kafka.zookeeper.connect` requirement from Tag Sync's Atlas Kafka source and fix Atlas Kafka consumer setup for Kafka 3.9+ / KRaft (PLAINTEXT and Kerberos). Fixes [RANGER-5658](https://issues.apache.org/jira/browse/RANGER-5658). ### Changes - **AtlasTagSource.java** — remove ZK validation; load config via ApplicationProperties; validate bootstrap servers + consumer group only - **setup.py** — emit Kerberos JAAS only for SASL protocols; fix rangerTagsync_password jceks credential - **Installer/templates** — drop TAG_SOURCE_ATLAS_KAFKA_ZOOKEEPER_CONNECT from install properties and templates - **ranger-tagsync-services.sh** — pass -Datlas.conf for Atlas properties - **AtlasTagSourceConfigTest.java** — unit tests for required Kafka properties - **dev-support/README-TAGSYNC-ATLAS-KAFKA-CONFIG.md** — operator documentation **Note:** AtlasTagSource.java conflict on backport was resolved by taking the #1037 version (includes formatting update from master). ## Test plan - [ ] `mvn test -pl tagsync -Dtest=AtlasTagSourceConfigTest -Drat.skip=true -Dcheckstyle.skip=true -Dpmd.skip=true -Dspotbugs.skip=true` - [ ] Fresh install: atlas-application.properties has bootstrap servers + consumer group, no atlas.kafka.zookeeper.connect - [ ] PLAINTEXT Atlas Kafka: Tag Sync starts and consumes entity notifications - [ ] Kerberos (SASL): JAAS entries present only when security protocol is SASL - [ ] CI build-8 green on ranger-2.9 -- 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]
