Pil0tXia opened a new pull request, #4468:
URL: https://github.com/apache/eventmesh/pull/4468
<!--
### Contribution Checklist
- Name the pull request in the form "[ISSUE #XXXX] Title of the pull
request",
where *XXXX* should be replaced by the actual issue number.
Skip *[ISSUE #XXXX]* if there is no associated github issue for this
pull request.
- Fill out the template below to describe the changes contributed by the
pull request.
That will give reviewers the context they need to do the review.
- Each pull request should address only one issue.
Please do not mix up code from multiple issues.
- Each commit in the pull request should have a meaningful commit message.
- Once all items of the checklist are addressed, remove the above text and
this checklist,
leaving only the filled out template below.
(The sections below can be removed for hotfixes of typos)
-->
<!--
(If this PR fixes a GitHub issue, please add `Fixes #<XXX>` or `Closes
#<XXX>`.)
-->
Fixes #<XXXX>.
### Motivation
This is a subtask of GLCC Subject
https://github.com/apache/eventmesh/issues/4040.
Design Document: https://docs.qq.com/doc/DSk9NU1JiRlBpSXln
`eventmesh-admin` module is going to be substituted to be deployed
independently. For now, a new module `eventmesh-admin-kotlin` is added to
migrate functions of `eventmesh-admin` gradually.
The `eventmesh-admin-kotlin` module used Gradle Kotlin DSL instead of Gradle
Groovy DSL to manage dependencies, because Kotlin DSL is the default Gradle DSL
currently and it has many advantages over Groovy DSL.
### Modifications
1. new feats
Subscription management functions are now available.
Connection management function will be finished after EventMesh K8s operator
is supported.
2. one change made to existing code
The `toString` method of `Session` now supports Json output in order to be
displayed on `eventmesh-dashboard`.
Before:
After:
### Todo
- Topic management functions in `storage-plugin.admin` will be migrated to
`eventmesh-admin-kotlin`.
- Endpoints in `runtime.admin` will use Netty instead of Sun HttpServer.
- Connection managment and etcd support.
### Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs /
not documented)
- If a feature is not applicable for documentation, explain why?
- If a feature is not documented yet in this PR, please create a followup
issue for adding the documentation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
For additional commands, e-mail: dev-h...@eventmesh.apache.org
