-
Notifications
You must be signed in to change notification settings - Fork 6
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
Provide LowKey Vault Test Container Package/Module for DotNet #1313
Comments
Hi @Xor-el , I cannot promise that I will succeed because I am not a .Net developer. As you might imagine, it will be a challenge for sure to accomplish this, but I will try to look into it and see what I can do. I think it would be best to implement this module in Testcontainers. As I see you have created an issue there as well: testcontainers/testcontainers-dotnet#1334 Please feel free to track these tickets for updates... Thank you! |
@nagyesta Thanks for the feedback. I also agree that it would be better suited to implement this in TestContainers like you mentioned. |
Thank you @Xor-el ! I am sure you have already found it, but just in case you didn't, this is the most interesting class of the Java Testcontainers module: https://github.com/nagyesta/lowkey-vault/blob/main/lowkey-vault-testcontainers/src/main/java/com/github/nagyesta/lowkeyvault/testcontainers/LowkeyVaultContainer.java Also, please feel free to reach out in case you are not sure how it works/should work! |
Hi @Xor-el , great news! Thank you for investing time and effort in this! |
Is your feature request related to a problem? Please describe.
It's currently cumbersome to perform integration tests for services that depend on Azure Key Vault. Although we can use LowKey Vault as a test double, the process requires manually starting the Docker image. This manual step disrupts the workflow and does not integrate seamlessly with our testing pipeline.
Describe the solution you'd like
A dedicated LowKey Test Container Package/Module for .NET that automates the setup and teardown of the LowKey Vault Docker container as part of the test lifecycle, simplifying integration testing for Azure Key Vault dependencies.
Describe alternatives you've considered
Manually starting the LowKey Vault Docker container prior to running tests, which is inefficient and prone to errors.
The text was updated successfully, but these errors were encountered: