...
Current state: Under Discussion
Discussion thread: TBD here
JIRA:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
- Can be sent to any broker
- If there are multiple instructions for the same resource in one request the extra request will be ignored
- This is because the list of resources is modeled server side as a set
- Multiple resources results in the same end goal, so handling this error for the user should be okay
- This is similar to how delete topics handles requests
- If the config_name array is null, all configs are returned. Otherwise, configs with the provided names are returned.
- Valid resource types are "Topic", "Client", "User" and "Broker".
- If resource_type is "Broker" and resource_name matches the broker that has received the request, read-only configs (i.e. configs that can only be defined statically, typically via server.properties) for this broker are also returned. Note that brokers are the only resource type with read-only configs at this point.
- The principal must be authorized to "ReadConfigs" on the "Cluster" resource ("ReadConfigs" is also included in the "All" operation). Unauthorized requests will receive a ClusterAuthorizationFailed error code.
- Errors are reported independently per resource.
...