WHAT

In some cases we give detailed information in PolicyViolationException messages about what the violation(s) was/were in Kafka (usually from kas-broker-plugins, e.g. here). Currently if requests going through kafka-admin-api
hit a PolicyViolationException, they don't pass this useful information back to the caller in the HTTP response, they just give a generic static message for all cases. The purpose of this task is to change it so the kafka-admin-api captures that info and includes it in the response.

WHY

User feedback has shown that the generic message is confusing, and it can take a while to figure out what the actual cause of the violation was.

HOW

medgar@redhat.com suggests that mapping the exception's message to the response's detail property should be a good solution.

This part of the code might be a good place to start looking.