Aias00 opened a new issue, #958: URL: https://github.com/apache/rocketmq-dashboard/issues/958
## Problem `GeneralSettingsVO.apiKey` is marked `@JsonProperty(access = WRITE_ONLY)` to keep the key out of API responses. `MybatisPlusSettingsRepository` persists the same object by calling `ObjectMapper.writeValueAsString(settings)`. Jackson therefore omits `apiKey` from the database JSON as well. After saving an OpenAI-compatible LLM configuration, the current process can use its in-memory override, but the key is absent after restart and the provider becomes disabled unless `RMQ_LLM_TOKEN` is configured. ## Scope Separate API-response redaction from persistence serialization so a configured key survives a settings repository round trip without being returned by REST APIs or emitted in `toString()`. ## Acceptance criteria - Saving and reloading `GeneralSettingsVO` through `MybatisPlusSettingsRepository` preserves a configured API key. - REST responses continue to expose only `apiKeyConfigured`, never the key value. - Add a persistence round-trip regression test. Related to #813 and #863, but specifically covers the API-key persistence regression introduced by the MySQL-backed settings repository. -- 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]
