lizhimins commented on PR #4390:
URL:
https://github.com/apache/rocketmq-dashboard/pull/4390#issuecomment-5755155322
Closing as not planned: Studio deliberately does not own broker / NameServer
/ proxy
lifecycle operations.
Those endpoints are stubs on purpose in the current trunk, and the UI points
operators at the deployment / ops platform, because restarting a broker or
creating, upgrading and deleting a NameServer changes the topology of a
cluster
that Studio only observes. Taking this PR would turn the console into a
control
plane for process lifecycle, which is a product decision we are not making.
Two secondary points for the record:
- it changes the REST response contract without updating `docs/api-spec.md`;
- 31 files / +1819 also carries deployment config changes
(`deploy/.env.example`, `deploy/README.md`, `deploy/docker-compose.yml`),
which is
more surface than a feature PR should have.
#4311 and #4355 stay open as feature requests — they are just not something
we plan
to support inside Studio itself.
The implementation quality here is genuinely good. If you want to contribute
in this
area, an ops-facing read-only view (what is running, which versions, config
drift
between the registry and the live cluster) is far more likely to land than
lifecycle
mutations, and it is the direction the existing cluster page is already
moving in.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
