You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generating Spring Cloud Stream code that leverages the Spring Cloud Stream Binder for Solace PubSub+ requires both @asyncapi/generator and @asyncapi/java-spring-cloud-stream-template packages.
It'd make it easier on systems teams if everything that was required to generate code was included in a single image and made available as a binary.
I've put together an example here that shows how to:
build an image that includes both the generator and template,
export the image to a .tar.gz
attach the .tar.gz to a release's assets
I suggest that we host a binary of the generator + SCS template on this repository until the official AsyncAPI repositories decide to host the image(s) themselves, I've engaged some of the AsyncAPI contributors on Slack and raised an issue here.
The text was updated successfully, but these errors were encountered:
@andrew-j-roberts - this is a great suggestion, but it does not belong to this repository. We suggest that you collaborate with our Dev. Advocate team on https://solace.community/ to raise this as an AsyncAPI feature.
Generating Spring Cloud Stream code that leverages the Spring Cloud Stream Binder for Solace PubSub+ requires both @asyncapi/generator and @asyncapi/java-spring-cloud-stream-template packages.
It'd make it easier on systems teams if everything that was required to generate code was included in a single image and made available as a binary.
I've put together an example here that shows how to:
I suggest that we host a binary of the generator + SCS template on this repository until the official AsyncAPI repositories decide to host the image(s) themselves, I've engaged some of the AsyncAPI contributors on Slack and raised an issue here.
The text was updated successfully, but these errors were encountered: