Aias00 opened a new issue, #1449:
URL: https://github.com/apache/rocketmq-dashboard/issues/1449

   Parent: #1312
   Depends on: #1448
   
   ## Problem
   
   Studio ACL CRUD currently reads and writes `AclRepository` records only. For 
Apache RocketMQ ACL 2.0, `MQAdminExt.listAcl` and `getAcl` can expose policy 
state from a Broker, but Studio has no instance-scoped provider that calls 
those APIs.
   
   ## Scope
   
   Add a read-only Apache ACL 2.0 provider behind the selected-instance runtime 
admin path. This issue intentionally excludes all remote mutations and ACL 1.0 
policy management.
   
   ## Acceptance criteria
   
   - The provider accepts an `instanceId` and rejects non-Apache instances or 
instances without a usable runtime AdminClient.
   - It uses `RuntimeAdminClientResolver` so the configured 
`adminCredentialRef` / RPC hook from #1448 is honored.
   - It discovers the selected instance's master Broker addresses and invokes 
`listAcl` or `getAcl` through the authenticated AdminClient.
   - The response keeps source provenance and per-Broker results: a remote 
failure is not represented as an empty policy list, and partial results are 
explicit.
   - Existing Studio-local ACL metadata remains available only through its 
existing local endpoints; it is never used as a fallback for a failed remote 
read.
   - The UI receives a read capability/status that distinguishes 
provider-backed remote data, local metadata, and unavailable/partial remote 
data.
   - Unit tests cover credential routing, complete results, partial Broker 
failures, and no-local-fallback behavior.
   
   ## Design notes
   
   `MQAdminExt.listAcl/getAcl` is the usable Apache ACL 2.0 admin surface. ACL 
1.0 has no equivalent cluster-wide policy list API, so it requires a separate 
configuration/file-backed provider design rather than being inferred through 
this provider.


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