[FEATURE] Add new secrets manager implementation (Azure Key Vault)

NishantJoshi00 commented 1 month ago

📝 Feature Description We need to expand our secrets manager support by integrating Azure Key Vault. Currently, our system supports three secrets manager interfaces: AWS KMS, Hashicorp Vault, and Plaintext. Adding Azure Key Vault will provide users with an additional option for securely storing sensitive configuration settings.

🔨 Possible Implementation

Research Azure Key Vault API and integration methods.
Develop a new secrets manager interface for Azure Key Vault, following the patterns established by existing integrations (AWS KMS, Hashicorp Vault).
Implement necessary authentication and access methods for Azure Key Vault.
Create functions to store, retrieve, and manage secrets using Azure Key Vault.
Ensure the new integration adheres to our existing security standards and practices.
Update configuration options to allow users to select Azure Key Vault as their secrets manager.
Develop comprehensive tests to verify the functionality and security of the Azure Key Vault integration.

🔖 Note: The implementation should maintain consistency with our existing secrets manager interfaces while accommodating any Azure Key Vault-specific features or requirements. Ensure that the integration is scalable and performant, considering potential high-load scenarios.

Submission Process:

Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
Once assigned, submit a pull request (PR).
Maintainers will review and provide feedback, if any.
Maintainers can unassign issues due to inactivity, read more here.
For this issue, please raise a PR to juspay/hyperswitch-card-vault.

Refer here for Terms and conditions for the contest.

NishantJoshi00 commented 1 month ago

Links to: https://github.com/juspay/hyperswitch-card-vault/issues/114