Hi community, I previously created DSIP-105 [1] to introduce sensitive variable support (masking in API/UI + encrypted storage) for DolphinScheduler. The design has been detailed in the issue, and I have also submitted an initial PR [2] for implementation.
However, the proposal hasn't received much feedback yet, and the PR is pending review. This is a feature we (CT Cloud / 天翼云) heavily need in production — we currently have secrets exposed in plaintext across workflow parameters. I'd appreciate it if community members could take a look and share your thoughts, especially on: - The `sensitive` boolean flag approach in the Property class - The `******` placeholder merge behavior on save - Reusing PasswordUtils for encryption (shared with datasource encryption config) If anyone is interested in co-reviewing or has concerns about the design, I'm happy to adjust. Looking forward to your feedback! [1] https://github.com/apache/dolphinscheduler/issues/17937 [2] https://github.com/apache/dolphinscheduler/pull/18329 Thanks, luxiaolong / det101
