Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to define MQTT User Properties in an AsyncAPI document? #1043

Closed
aysancag opened this issue Mar 13, 2024 · 2 comments
Closed

How to define MQTT User Properties in an AsyncAPI document? #1043

aysancag opened this issue Mar 13, 2024 · 2 comments
Labels

Comments

@aysancag
Copy link

Hi,

I am working on defining a spec for a service that operate over MQTT using AsyncAPI. We defined messages that use MQTT v5 user properties described here: https://www.hivemq.com/blog/mqtt5-essentials-part6-user-properties/

However, we weren't able to find how to correctly define the User Properties in the AsyncAPI specification. We defined them in Headers for now, but I am not sure if that is the correct approach. Is there way to define them currently?

I found these related issues:
#878
asyncapi/bindings#201

Copy link

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.

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jul 12, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant