-
Notifications
You must be signed in to change notification settings - Fork 56
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
Add messages header that points to the Python package for the schema #187
Labels
Comments
Can I work on this issue @jeremycline? |
Hi @Rits1272, I no longer have the time to work on this project so I can't commit to walking you through the necessary steps for this. Nor am I sure that anyone is around to review your work, accept it, and then release it. However, no one else is working on this as far as I know so if it's something you'd like to do despite those things, you're more than welcome to. |
abompard
added a commit
to abompard/fedora-messaging
that referenced
this issue
Jul 5, 2024
Fixes: fedora-infra#187 Signed-off-by: Aurélien Bompard <[email protected]>
abompard
added a commit
to abompard/fedora-messaging
that referenced
this issue
Jul 5, 2024
Fixes: fedora-infra#187 Signed-off-by: Aurélien Bompard <[email protected]>
abompard
added a commit
to abompard/fedora-messaging
that referenced
this issue
Jul 5, 2024
Fixes: fedora-infra#187 Signed-off-by: Aurélien Bompard <[email protected]>
abompard
added a commit
to abompard/fedora-messaging
that referenced
this issue
Jul 5, 2024
Fixes: fedora-infra#187 Signed-off-by: Aurélien Bompard <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Publishers using schema add a header to identify the schema, but from the consumer side it's not obvious where to get the schema.
We can use the entry point of the message being published to inspect that package's metadata and provide things like the URL and so on. Then on the consumer side we can log more helpful messages when users are missing the schema.
The text was updated successfully, but these errors were encountered: