Apache Camel logs the JSON message body before it converts to the Java BieMessagePayload class. This process ignores some restrictions we introduced in the Java class via annotations, causing some fields that we do not want to show in the logs to be printed out as well.
Associated tickets or Slack threads:
2810
How does this fix it?[^1]
Removed logging of the JSON string; only log once the JSON string is converted into our Java class.
How to test this PR
Verify in the example-workflow log that no description field is displayed.
What was the problem?
Apache Camel logs the JSON message body before it converts to the Java
BieMessagePayload
class. This process ignores some restrictions we introduced in the Java class via annotations, causing some fields that we do not want to show in the logs to be printed out as well.Associated tickets or Slack threads:
2810
How does this fix it?[^1]
Removed logging of the JSON string; only log once the JSON string is converted into our Java class.
How to test this PR
description
field is displayed.[^1]: Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. [^secrel]: To check if a PR will succeed in the SecRel workflow, test PRs in the SecRel pipeline.