Replies: 1 comment 1 reply
-
Hey @iMacTia ! These are all great questions and I have responses, but would you mind breaking these up into multiple topics? I think the discussion might get too unwieldy otherwise. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We use a remote schema registry (Confluent Cloud) in our application, and it's really handy to have an integration with it in the first place. However, the process for importing new schemas into the application currently presents some friction points:
deimos
was able to get them directly from the schema registry instead! Is there any reason why that's not possible at the moment?deimos
to only read from the schema registry and use that during the validation of a message (e.g. compare the auto-generated ruby class and warn when the application is producing using an outdated schema) without updating the schema registry in the processorg.company.my_schemas
). This means that schema files need to go into a nested folder structure (e.g.org/company/my_schemas
). The auto-generated Ruby class gets placed alongside the schema file, but the onlymodule
in the file ismodule Schemas
. This breaks Rails auto-loading, which won't be able to find these classes. So we manually move them to a different location, but that means every time therake deimos:generate_schema_classes
is executed, it will re-create all the schemas that were previously moved. The solution here would be to either include the schema namespace in the ruby filemodule
s, or create the ruby file in the root (specified in the Deimos config).Based on the feedback on these points, I'd be happy to work on some improvements PRs 🙌
Beta Was this translation helpful? Give feedback.
All reactions