Quarkus Asyncapi Scanner
This extension creates an AsyncApi-document, describing data your server publishes/subscribes to/from Kafka-topics.
It does this by
-
scanning for annotations
@Channel, @Outgoing and @Incoming
in your project, -
reading topics and descriptions from microprofile-configuration and
-
reading data from running kafka
The result can be viewed as html or svg or downloaded as yaml, json or plant-uml (localhost://[quarkus.http.root-path]/asyncapi.[html|svg|yaml|json|puml]).
Installation
If you want to use this extension, you need to add the io.quarkiverse.asyncapi:quarkus-asyncapi
extension first to your build file.
For instance, with Maven, add the following dependency to your POM file:
<dependency>
<groupId>io.quarkiverse.asyncapi</groupId>
<artifactId>quarkus-asyncapi-scanner</artifactId>
<version>1.0.2</version>
</dependency>
Extension Configuration Reference
For more information about the extension configuration please refer to the Configuration Reference. |
Configuration property fixed at build time - All other configuration properties are overridable at runtime
Type |
Default |
|
---|---|---|
Enable AysncApi-Scanning Environment variable: |
boolean |
|
Version of the WebComponent to be used in html-view to be found at [HOST]/asyncapi.html Environment variable: |
string |
|
Full qualified name of the implementing AsyncApiFilter Environment variable: |
string |
|
AsyncApi specification version Environment variable: |
string |
|
Default ContentType Environment variable: |
string |
|
Title Environment variable: |
string |
|
Project-version Environment variable: |
string |
|
Project-description Environment variable: |
string |
|
Contact-Name Environment variable: |
string |
|
Contact-Email Environment variable: |
string |
|
Contact-URL Environment variable: |
string |
|
License-Name Environment variable: |
string |
|
License-URL Environment variable: |
string |
|
Url Environment variable: |
string |
required |
Protocol Environment variable: |
string |
|
Description Environment variable: |
string |
Migration to V1 (switch from AsyncApi v2.6.0 to v3.0.0)
The structure of asyncApi has multiple breaking changes. See migration to V3 for details. To apply to these changes following changed in the extension-configuration:
-
server.url
is divided intoserver.host
andserver.pathname
(see server-url splitting up)