Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: azure-key-vault driver #159

Merged
merged 10 commits into from
Feb 27, 2023
Merged

feat: azure-key-vault driver #159

merged 10 commits into from
Feb 27, 2023

Conversation

itpropro
Copy link
Member

No description provided.

@itpropro itpropro requested a review from danielroe February 20, 2023 21:03
@danielroe danielroe changed the title feat(driver): Added Azure Kay Vault driver feat(driver): azure-key-vault driver Feb 20, 2023
@danielroe danielroe changed the title feat(driver): azure-key-vault driver feat(driver): azure key vault driver Feb 20, 2023
Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me! what about something like https://github.com/peveuve/ms-vault-mock for testing?

itpropro and others added 4 commits February 20, 2023 22:35
@itpropro
Copy link
Member Author

itpropro commented Feb 20, 2023

looks good to me! what about something like https://github.com/peveuve/ms-vault-mock for testing?

Great find, I will check that. The main problem would be that it hides the actual slowness of Azure Kay Vault, but for unit testing it's great.

@itpropro
Copy link
Member Author

looks good to me! what about something like https://github.com/peveuve/ms-vault-mock for testing?

I tested that and it's quite complex to get it to run with the current version of Key Vault packages, as you have to generate cert pairs, disable HTTPS validation and create some workaround due so recent API changes. The package wasn't updated for two years, which means there are a lot of old and complex dependencies from lodash to express and the Key Vault API itself is also old and has no support for purge and soft delete.
I would prefer a free Key Vault hosted instance tbh @danielroe

@pi0 pi0 changed the title feat(driver): azure key vault driver feat: azure-key-vault driver Feb 27, 2023
Copy link
Member

@pi0 pi0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks (also skipping tests for now. trusting it works as expected)

@pi0 pi0 merged commit 24e1c7b into main Feb 27, 2023
@pi0 pi0 deleted the feat/azure-key-vault branch February 27, 2023 19:51
@itpropro
Copy link
Member Author

Thanks (also skipping tests for now. trusting it works as expected)

The only thing about this driver (different to my other PRs) is that Azure Key Vault is a very slow service. The clear action can take a minute, although I tried to make it at least a little better with concurrency.
It’s also in the README, but if you don’t like it, because of the actual service slowness, we can revisit it.

@pi0
Copy link
Member

pi0 commented Feb 28, 2023

Slowness is okay and i guess somehow expected for encryption. As long as we can test locally we can add some additional tests only running in CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants