det101 opened a new issue, #17937: URL: https://github.com/apache/dolphinscheduler/issues/17937
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Add a new variable type `Sensitive Variable` for securely storing sensitive information like passwords. This can prevent sensitive content from appearing in logs and the UI. It is recommended to reuse the existing encryption and decryption mechanism implemented for data sources. ### Use case Currently, the project only supports a single type of variable for general use. However, in real-world scenarios, sensitive data such as database passwords or API keys often needs to be stored. Storing such sensitive information as common variables may lead to potential security risks such as exposure in logs or the UI. Adding a `Sensitive Variable` type can ensure that this type of content remains hidden in logs and the UI, improving platform security. ### Related issues None ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
