btlqql opened a new issue, #439: URL: https://github.com/apache/rocketmq-dashboard/issues/439
## Problem The Studio K8s certificate page imports `mockK8sCerts` directly and performs edit and delete operations only against component state. The add button is also a placeholder. As a result, production builds never call the existing `/api/k8s-certs` endpoints, so users see sample certificates instead of server data and all mutations disappear after a reload. The API module already exposes list, create, update, renew, and delete operations, and the server implements the matching controller and service. ## Expected behavior - Load certificates through the service layer so `VITE_USE_MOCK` controls the data source. - Show a loading state and surface request failures. - Create, update, and delete certificates through the backend in production mode. - Update the table only after the server operation succeeds. - Keep CRUD behavior usable and persistent within the in-memory mock store when mock mode is enabled. - Return created, updated, and renewed certificate records from the API wrappers. ## Validation Add frontend API contract tests for list, create, update, and delete request/response handling, then run the full frontend test, lint, and production build commands. -- 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]
