-
Notifications
You must be signed in to change notification settings - Fork 639
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
[ISSUE #435] Initial Creation of eventMesh-admin module in EventMesh #513
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to discuss, whether we need to add a new control panel module
@qqeasonchen @ruanwenjun Yes, eventmesh-admin sounds a good idea. I will rework this PR to contribute eventmesh-admin module. |
@qqeasonchen I think you are right. Putting schemaregistry in this pr could be confusing. My thought was that schemaregistry may be a child module of the eventmesh-admin module. Therefore, I defined the schemaregistry REST APIs in the readme file of this commit. :) |
@yzhao244 thanks,about schemaregistry, @JunjieChou is working on this too, i suggest we discuss first to decide how to provide service, lonely or in runtime, is it ok? btw, if you have wechat, you can add eventmesh helper or we can have a online meeting. |
@yzhao244 @JunjieChou
|
@qqeasonchen @ruanwenjun @JunjieChou @jinrongluo |
@yzhao244 @qqeasonchen @ruanwenjun |
Currently, I have created a separated running schemaregistry based on springboot. The left APIs that I haven't accomplished are related to compatibility checks. It is hard and I'm surveying methods for that. |
@qqeasonchen @ruanwenjun @jinrongluo If I am not mistaken, I think it makes sense that schema registry can be run as a seperate service which is out of runtime. Also it can be implemented by using SpringBoot as @JunjieChou is doing.. Therefore, I have removed schema registry APIs out of the readme in eventmesh-admin module and keep this PR only focusing on Admin APIs. |
@yzhao244 @JunjieChou Be careful to make the git commit message clear if your two person submit to one branch, then the community can directly merge to development branch, the all commit log can retain. Otherwise, community will use squash merge, then the all commit log will be merged into one, this means one person's contribution will lose. This often happens in other community. |
@ruanwenjun OK, that's indeed a thing needed to be taken into consideration. Also, @yzhao244 I have a proposal for our division of work.
If you would like to do the first one, that you just need to modify the persistence layer and combine the codes with admin module. And I will continue the second one. You are the first contributor to this series of issues, so you get the option! 🤣 |
Codecov Report
@@ Coverage Diff @@
## develop #513 +/- ##
==========================================
Coverage 10.42% 10.42%
Complexity 328 328
==========================================
Files 241 241
Lines 11737 11737
Branches 1001 1001
==========================================
Hits 1224 1224
Misses 10411 10411
Partials 102 102
Continue to review full report at Codecov.
|
@yzhao244 @JunjieChou hi, admin moucle may neet plugin too, like eventmesh-admin-rocketmq, which used to managen topics or other management functions. |
@qqeasonchen @JunjieChou Yes, you are right. Under eventmesh-admin module, we can manage to create sub modules/plugins such as eventmesh-admin-rocketmq for managing topics and even subGroups. Regarding this PR, it only contains eventmesh-admin module plus readme. |
@JunjieChou you can go ahead do the schema registry since you are already working on implementing the schema registry by using SpringBoot and sounds you already have coding done lol.. Therefore, please work on the schema registry part. |
@yzhao244 ok, if there are no more code to be committed to this PR, it can be merged then, and waiting for the plugins. |
@qqeasonchen Yes, you are right.. For this PR, there are no more code to be committed. :) .. I will be working on plugins and push via another PR. thx |
…tMesh (apache#513) * initial checkin of eventmesh-schema-plugin * add file header * rework pr to add eventmesh-admin module * typo in readme * add topic rest apis in readme * add topic rest apis in readme * move schema registry out of this pr * move schema registry out of this pr
…513) * initial checkin of eventmesh-schema-plugin * add file header * rework pr to add eventmesh-admin module * typo in readme * add topic rest apis in readme * add topic rest apis in readme * move schema registry out of this pr * move schema registry out of this pr
Fixes ISSUE #435 #346
Motivation
The purpose of this PR is for contributing eventmesh-admin module which includes initial draft of readme file for describing REST APIs
Modifications
A new eventmesh-admin is created along with a readme file includes REST APIs.
Documentation