Page History

...

DescribeConfigs Request (Version: 0) => [resource [config_name]]   
  resource => resource_type resource_name
    resource_type => INT8
    resource_name => STRING
  config_name => STRING

Request semantics:

1. Can be sent to any broker
2. 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
3. If the config_name array is null, all configs are returned. Otherwise, configs with the provided names are returned.
4. Valid resource types are "Topic", "Client", "User" and "Broker".
5. If resource_type is "Broker" and resource_name matches the broker that has received the request, read-only configs for this broker are also returned.
6. 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.
7. Errors are reported independently per resource.

...