If the quarkus-apicurio-registry-avro
extension is present, Dev Services for Apicurio Registry automatically starts an Apicurio Registry instance in dev mode and when running tests.
Also, all Kafka channels in SmallRye Reactive Messaging are automatically configured to use this registry.
(This automatic configuration of course only applies to serializers and deserializers from the Apicurio Registry Avro library.)
Enabling / Disabling Dev Services for Apicurio Registry
Dev Services for Apicurio Registry is automatically enabled unless:
-
quarkus.apicurio-registry.devservices.enabled
is set tofalse
-
mp.messaging.connector.smallrye-kafka.apicurio.registry.url
is configured -
all the Reactive Messaging Kafka channels have the
apicurio.registry.url
attribute set
Dev Services for Apicurio Registry relies on Docker to start the registry. If your environment does not support Docker, you will need to start the registry manually, or use an already running registry. You can configure the registry URL for all Kafka channels in SmallRye Reactive Messaging with a single property:
mp.messaging.connector.smallrye-kafka.apicurio.registry.url=http://localhost:8081/apis/registry/v2
Setting the port
By default, Dev Services for Apicurio Registry picks a random port and configures the application.
You can set the port by configuring the quarkus.apicurio-registry.devservices.port
property.
Note that the Kafka channels in SmallRye Reactive messaging are automatically configured with the chosen port.
Configuring the image
Dev Services for Apicurio Registry uses apicurio/apicurio-registry-mem
images.
You can select any 2.x version from https://hub.docker.com/r/apicurio/apicurio-registry-mem:
quarkus.apicurio-registry.devservices.image-name=apicurio/apicurio-registry-mem:latest-snapshot