[RFC] Create Anypoint MQ protocol and bindings

[GeraldLoeffler]

In trying to create AsyncAPI documents that assume Anypoint MQ as the message broker, It became apparent that this is not possible without binding objects for a new protocol for that broker.

I request anypointmq to be added to the list of protocols in AsyncAPI, and corresponding binding objects to be defined and added to https://github.com/asyncapi/bindings. These binding objects should describe, among other things:

1. how to connect to an AnypointMQ broker instance using the server object
2. how to use AnypointMQ queues (FIFO or not) and exchanges as channels
3. how to use AnypointMQ message specifics like user properties, message ID, et.

[GeraldLoeffler]

Development of the requested bindings has been started in https://github.com/integrational/asyncapi-bindings/tree/master/anypointmq and a PR will be sent once sufficiently progressed.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.

Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[GeraldLoeffler]

will submit a minimal PR shortly

[GeraldLoeffler]

This issue is addressed by these 2 PRs:

• against the spec repo: feat: add Anypoint MQ protocol to list of supported bindings #545
• against the bindings repo: feat: create Anypoint MQ bindings bindings#63

[GeraldLoeffler]

This PR asyncapi/spec-json-schemas#67 covers the addition of the anypointmq protocol to the AsyncAPI JSON schema

[GeraldLoeffler]

For reference: the AsyncAPI team has rejected the need for anypointmq as a protocol because the interaction with the Anypoint MQ broker is based on HTTP (for which a protocol already exists). I think this rejection stems from a basic disagreement about the purpose of a "protocol" in AsyncAPI. See asyncapi/bindings#63 (comment)

[derberg]

@GeraldLoeffler the PR is not closed without merge, thus it is not rejected 😉 it is in progress

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[derberg]

@GeraldLoeffler do you continue this one?

[GeraldLoeffler]

@GeraldLoeffler do you continue this one?

as far as i'm aware @derberg this is complete in all its aspects: it just needs merging (into the spec and bindings repos).

[derberg]

PR in the binding repo is still not merged, there are some comments form my side

[GeraldLoeffler]

PR in the binding repo is still not merged, there are some comments form my side

oh i see - i thought this had been accepted weeks/months ago. I'll review your comments and incorporate them if possible.

[GeraldLoeffler]

PR in the binding repo is still not merged, there are some comments form my side

done

[derberg]

@GeraldLoeffler we are almost there. PR on binding repo is perfect. PR here in spec repo needs minor change (left comment) and we are missing PR to change JSON Schema, PR against 2021-09-release branch in https://github.com/asyncapi/spec-json-schemas. You can have a look on PR from Dale on IBM MQ binding to see how this should be changed so we see in PR only specific changes (you will need to create new JSON Schema file for new 2.2.0 version, this will be first commit, and then in the 2nd commit add new binding please)

[GeraldLoeffler]

@GeraldLoeffler we are almost there. PR on binding repo is perfect. PR here in spec repo needs minor change (left comment) and we are missing PR to change JSON Schema, PR against 2021-09-release branch in https://github.com/asyncapi/spec-json-schemas. You can have a look on PR from Dale on IBM MQ binding to see how this should be changed so we see in PR only specific changes (you will need to create new JSON Schema file for new 2.2.0 version, this will be first commit, and then in the 2nd commit add new binding please)

i think i've now done all that @derberg . See asyncapi/spec-json-schemas#90 for the JSON Schema PR, and also note the strange files that appeared in that PR (asyncapi/spec-json-schemas#90 (comment)).

[GeraldLoeffler]

note the strange files that appeared in that PR (asyncapi/spec-json-schemas#90 (comment)).

all cleaned-up, all ready: i assume this will go into 2.2.0?

[dalelane]

@GeraldLoeffler Is there anything left to do for this issue or do you think it's okay to close?

[GeraldLoeffler]

that's been implemented @dalelane and i wasn't aware that there was this issue left open: please close it. Thank you.

[dalelane]

@derberg can you close, please? (I don't have the power 😁)