[PR] [test][broker] Reproduce shared topic permission deletion [pulsar]

["mattisonchao (via GitHub)" <gi...@apache.org>]

mattisonchao opened a new pull request, #26435:
URL: https://github.com/apache/pulsar/pull/26435

   ## Motivation
   
   In a multi-cluster deployment with separate local metadata stores and a shared configuration metadata store, topic-level permissions are shared even though topic lifecycles remain local. Deleting a topic in one cluster currently removes the shared permission entry while the same-named topic remains available in another cluster.
   
   This draft adds a deterministic regression reproducer before the behavior is corrected.
   
   ## Modifications
   
   - Add a two-broker integration test using the existing shared-configuration-store fixture.
   - Create the same topic in both clusters, grant topic-level permissions through one cluster, and verify they are visible through the other.
   - Delete the topic from one cluster, verify the peer topic still exists, and assert that its permissions remain.
   
   ## Testing
   
   - `gradle :pulsar-broker:checkstyleTest` passes.
   - `gradle :pulsar-broker:test --tests "org.apache.pulsar.broker.service.OneWayReplicatorUsingGlobalZKTest.testDeletingTopicOnOneClusterKeepsSharedTopicPermissions" -PtestRetryCount=0` reproduces the issue: the peer topic remains, but its permissions are `{}`.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org