...
ListAclsResponse (Version: 0) => error_code error_message [resource]
error_code => INT16
error_message => NULLABLE_STRING
resource => resource_type resource_name [acl]
resource_type => INT8
resource_name => STRING
acl => principal host operation permission_type
principal => STRING
host => STRING
operation => INT8
permission_type => INT8
The error_code field will be non-zero if there was an error processing the request. If the error_code is non-zero, the results list will be empty. Otherwise, each listed resource object describes a specific resource, and the ACLs bound to that resource. Note that if filters were specified in the ListAclsRequest, this may not be a complete list of all the ACLs bound to the resource, but only the ones which matched the supplied filters. None of the fields in the ACL 4-tuple or the resource 2-tuple are ever set to null or none in the response.
...
CreateAclsResponse (Version: 0) => [creation_response]
additioncreation_response => error_code error_message
error_code => INT16
error_message => NULLABLE_STRING
...
DeleteAclsResponse (Version: 0) => [filter_response]
filter_response => error_code error_message [match]
error_code => INT16
error_message => NULLABLE_STRING
match => error_code error_message resource_type resource_name principal host operation permission_type
error_code => INT16
error_message => NULLABLE_STRING
resource_type => INT8
resource_name => STRING
principal => STRING
host => STRING
operation => INT8
permission_type => INT8
Filter responses will be appear in the same order which the filters appeared. If the filter_response has a non-zero error_code, that means that the filter could not be applied by the server, and the match array will be empty. Otherwise, the match array contains a list of all the ACLs that matched the filter. Each match will have a non-zero error code and error message if it could not be removed. When a filters fails to match an ACLs, it is not an error. This will simply result in getting back a filter_response with an empty match list.
...