WHAT

Handle non-string data for a message's key, value, and header values. When one of the included data values cannot be read as a UTF-8 string (confirm), the string "Binary format not supported" (confirm) will be returned instead.

WHY

Avoid general error responses when a message contains binary data.

HOW

Read each value sequentially. If an invalid character exception occurs, stop reading and use the predetermined constant indicating binary data.

DONE

Include the following where applicable:

• <bulleted list of functional acceptance criteria that need to be completed>
• <call out anything on the documentation side that's needed as a result of this task being completed>
• <any metrics, monitoring dashboards and alerts that need to be created or be updated>
• <SOP creation or updates>

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged