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

ASYNCAPI 2 Schema registry stand alone module #1872

Open
rgranadosd opened this issue Apr 24, 2023 · 1 comment
Open

ASYNCAPI 2 Schema registry stand alone module #1872

rgranadosd opened this issue Apr 24, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@rgranadosd
Copy link

We find very useful this new feature, but I doesn't 100% in our use case. To be honest is a great idea, but maybe having and stand alone module to obtain the schema from asyncapi definition could be enough for us.

This is our use case :

Our Current Use Case:

  • Users define their events in avro format in their API repository. When they want to publish their schemas they call a job that executes several actions, some of them being:

    1) A custom library is called that merge all files with the definitions, including both the common metadata for all company events and the specific payload for each project, and generates the schema to be published in the schema registry.
    2) The schema is validated and compatibility (FORWARD_TRANSITIVE) is checked. If compatibility condition is not met the job fails
    3) Once everything has been validated the schema is published in the schema registry
    

  • Our users can define their schemas for both on Prem and Cloud environments (though even for cloud environment we are not using confluent cloud schema registry) and we use a custom subject naming strategy as we need to assign the same subject to multiple topics.
        

Request:    

Being able to allow users to define their events only in AsyncAPI form instead of avro will make their job easier so we would like to be able to use the AsyncAPI CLI tool, having just the tool that converts from AsyncAPI definition into an schema as a stand alone module would also be quite helpful as we would be able to integrate that functionality into our process.

If it's not possible, maybe could be a good point to:

  • Being able to configure some of the process steps like the schema registry endpoint or the subject naming strategy, as we need to be able to call on prem SRs and we use a custom naming strategy.
  • Being able to define which steps we want to execute: There are several steps we don't allow, like automatic topic creation, changing compatibility mode or flag creation.

Please don't hesitate to ask anything,
Thanks
 

@brianstrauch brianstrauch assigned kcorman0 and unassigned pagrawal10 May 9, 2023
@brianstrauch brianstrauch added the enhancement New feature or request label May 9, 2023
@brianstrauch
Copy link
Member

Thanks for opening this issue! We've added it to our roadmap and will provide updates here when we start working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants