Investigate using Microcks and asyncapi.com for docs and test automation

[afrittoli]

Following up the presentation by the Microcks team to the SIG events, there is an opportunity for use to improve our documentation automation as well as testing through functionality provided by Microcks and asyncapi.com

[yada]

https://www.asyncapi.com not async.io I guess ;-)

[afrittoli]

Thank you @yada, fixed now

[derberg]

do you need a hand with AsyncAPI? one of the maintainers here 👋🏼 I can hop on a call if ya need something

[e-backmark-ericsson]

@derberg , thanks for reaching out!

Given what was discussed on the SIG Events meeting where Microcks presented its solution and AsyncAPI, I believe one thing to start looking into would be how to formalize our Cloudevents binding specification of CDEvents, using AsyncAPI. If you'd look at https://github.com/cdevents/spec/blob/main/cloudevents-binding.md, what would a formal AsyncAPI specification of that binding look like?

[e-backmark-ericsson]

Also, what possibilities could AsyncAPI provide in order to generate a documentation for our JSON schemas? I understood from the meeting held with Microcks that there is a possibility to at least include example structures as part of the AsyncAPI spec, which are not actually part of the JSON schemas, to include them in a generated documentation of the spec. How would that be realized?

Would it be possible to generate something similar to a document like this https://github.com/cdevents/spec/blob/main/source-code-version-control.md from an AsyncAPI specification of the included events, for example corresponding to a JSON schema of an event like this: https://github.com/cdevents/spec/blob/main/schemas/changecreated.json ?

[afrittoli]

It took us a while, but we discussed this in cdevents/implementation-wg#5 and decided that asyncAPI would work for CDEvents.
@davidB @xibz do you want to use this issue to track the implementation?