Aias00 opened a new issue, #876:
URL: https://github.com/apache/rocketmq-dashboard/issues/876
### Before Creating the Bug Report
- [x] I found a bug, not just asking a question, which should be created in
GitHub Issues.
- [x] I have searched the existing issues and believe this is not a
duplicate.
- [x] I have confirmed that this bug belongs to the current repository.
### Describe the Bug
The RocketMQ Studio SSL settings page still simulates a successful save with
a local `setTimeout` and then updates only component state:
```tsx
setTimeout(() => {
setLoading(false);
message.success(t('ssl.saveSuccess'));
setSslConfig({ ...sslConfig, ...values });
}, 1000);
```
There is no backend API call or persistence layer behind this action. Users
can enable TLS/SSL in the UI and see a success message even though the server
configuration is not changed.
### Expected Behavior
Until a real SSL configuration API exists, the page should not report a
successful save. It should explicitly show that SSL settings persistence is
unavailable instead of mutating local state as if the configuration was applied.
### Scope
RocketMQ Studio Track 1 / BASE-01 HTTPS/SSL management baseline. The fix
should be small and avoid introducing a fake backend contract.
### Proposed Fix
Replace the simulated save path with a clear unavailable/error message and
keep the current displayed config unchanged. Add a frontend regression test
that verifies the success toast is not shown and the local settings are not
mutated.
--
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]
