wtybxqm opened a new issue, #9687: URL: https://github.com/apache/seatunnel/issues/9687
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description Currently, in Apache SeaTunnel's task configuration, sensitive information such as data source usernames and passwords is directly written into task scripts. This approach presents the following issues: - Security Risks: Sensitive information exposed in scripts may lead to data source leaks. - Maintenance Challenges: When data source configurations change, manual modifications are required across all related task scripts, resulting in inefficiency and a high risk of errors. To address these problems, this issue aims to integrate metalake to centralize the storage and management of data source information. By introducing a data source ID mapping mechanism, users can easily update and manage configurations. The goal is to support mainstream data catalogs like Apache Gravitino while providing extensible interfaces for future integration with third-party services (e.g., Unity Catalog or DataHub). ### Usage Scenario _No response_ ### Related issues https://github.com/apache/seatunnel/issues/8502 ### 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]
