aakamara23 opened a new pull request, #10962:
URL: https://github.com/apache/seatunnel/pull/10962
Purpose of this pull request
This PR is for issue #10309.
I added initial Azure Key Vault support to SeaTunnel using the existing
ConfigShade framework.
For this implementation, I:
- Added an `azure-kv` ConfigShade provider
- Added Azure Key Vault and Azure Identity dependencies
- Configured secret resolution using `vault.url`
- Registered the provider in the ConfigShade service file
The goal is to allow users to store sensitive values in Azure Key Vault
instead of directly in configuration files.
Does this PR introduce _any_ user-facing change?
Yes.
Users can now configure `shade.identifier = "azure-kv"` and reference
secrets stored in Azure Key Vault.
How was this patch tested?
I tested the changes locally by running:
mvn -pl seatunnel-core/seatunnel-core-starter test -DskipITs -DskipShade
-Dspotless.check.skip=true -U
The build completed successfully.
--
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]
