njnu-seafish opened a new pull request, #18386: URL: https://github.com/apache/dolphinscheduler/pull/18386
<!--Thanks very much for contributing to Apache DolphinScheduler, we are happy that you want to help us improve DolphinScheduler! --> ## Was this PR generated or assisted by AI? NO ## Purpose of the pull request close #17813 ## Brief change log Based on the feedback in issues like #17813 and #18004, users are currently prone to accidentally overwriting the correct password due to the mask. This misoperation is highly likely to cause data source password anomalies in scheduled SQL tasks, compromising the stability of the production environment. As previously discussed, One effective approach I can think of is to return an empty password field each time, meaning the interface never returns the password. Whenever the data source is updated, the password must be re-entered. When the user clicks edit, the backend returns an empty password (password: ""). This leaves the frontend password field blank. If the user saves directly, the frontend sends password: "", and the backend detects the empty value and retains the existing password in the database. ## Verify this pull request <!--*(Please pick either of the following options)*--> This pull request is code cleanup without any test coverage. *(or)* This pull request is already covered by existing tests, such as *(please describe tests)*. (or) This change added tests and can be verified as follows: <!--*(example:)* - *Added dolphinscheduler-dao tests for end-to-end.* - *Added CronUtilsTest to verify the change.* - *Manually verified the change by testing locally.* --> (or) ## Pull Request Notice [Pull Request Notice](https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/join/pull-request.md) If your pull request contains incompatible change, you should also add it to `docs/docs/en/guide/upgrade/incompatible.md` -- 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]
