Is it true that protobuf-plugin requires protobuf proto3, which requires schema-registry to work? Is there a good local docker schema-registry image I can use? I use confluentinc/cp-schema-registry:7.3.1 from docker-compose.yml and https://github.com/codingharbour/kafka-protobuf.git but ProtobufProducer and ProtobufConsumer don't work with schema-registry via http://localhost:8081. I verify that kafka container can produce and consume messages, and it receives protobuf from ProtobufProducer.

Yes, protobuf plugin only supports proto3.

I don’t think we have integrated to the schema registry. Is that a requirement to use proto3? I don’t think so. I assume you’re referring to Kafka though, but I’m still unsure why the schema registry would be part of a pact test

Yes, kafka with protobuf proto3 will talk to schema-registry to create/retrieve schema id for both consumer and producer to handle compatibility.

Do your tests need to include that part? Presumably you could reduce the scope of your tests? Have you looked at how message pact works? (see 👇 howtomessagepact)