krutoileshii commented on issue #10309: URL: https://github.com/apache/seatunnel/issues/10309#issuecomment-3746180057
Before jumping into one for for key vault, I'm trying to write one for simply AES encrypting them with a key stored on the server/client (In Config File). What would be the best way to do this? Would it make sense to read it from seatunnel.yaml or instead just have a separate config for the encryption key? Figured if i get that working first, the key-vault would be second. A couple things I am trying to do with that right now: 1. Encryption string stored in config file or ENV Var 2. Same key could be used across all nodes to share easily. Once I can get it working properly with AES, I would probably use same type of setup for KeyVault. Now given that this is a plugin, what would be the best way to get it included by default into the project? I think it would be beneficial to have at least basic encryption in place beyond the base64. -- 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]
