Avro message publication fails with no schema found

[lbroudoux]

Describe the bug

Trying the use-case defined into Avro/Kafka Guide and ends up with no schema published into Apicurio Registry and no message published on Kafka broker.

I've used docker-compose installation for that with custom application.properties:

%docker-compose.kafka.schema.registry.url=http://localhost:8888/api
%docker-compose.kafka.schema.registry.confluent=false

%docker-compose.minion.default-avro-encoding=REGISTRY

Expected behavior

We should have the registry updated with a new schema for the UsersignedupAvroAPI-0.1.2-user-signedup topic. We should also receive new messages on this topic.

Actual behavior

The microcks-async-minion pod fails publication with this exception:

2023-06-23 13:53:46,595 ERROR [io.git.mic.min.asy.pro.ProducerManager_Subclass] (QuarkusQuartzScheduler_Worker-5) Exception while converting {{"fullName":"John Doe","email":"john@microcks.io","age":36}} to Avro using schema {null}

How to Reproduce?

Replay use-case from above mentioned guide.

Microcks version or git rev

1.7.1

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

docker-comspoe

Additional information

MIght be a regression due to #782