Feature Request: Add built-in transformation for avro to json

[snuggie12]

Feature Request: Add built-in transformation for avro to json

[ynovytskyy]

Sounds like it could cover common integration use case:
PubSub (or other source) message with AVRO payload -> broker with AVRO-to-JSON -> HTTP target pointing to where JSON is expected as REST body/input

Looking at https://docs.triggermesh.io/1.26/transformation/other/xslttransformation/, AVRO-to-JSON could be quite similar. It requires 2 pieces of information:

• payload - AVRO payload (similar to XML input in xslttransformation) comming with each message
• metadata - AVRO schema (similar to XSLT in xslttransformation) to able to parse payload and produce JSON

[sebgoa]

When you can confirm that you are using triggermesh and that we can use your logo we will address this issue at no cost.
thank you