[RFE] Use localstack to validate smoke tests for azure key vault

[sanjay7178]

Similar to #41

Need to implement for azure key vault , I seen the docs for azure key vault is bit unclear in localstack , needed to research for it

References :

• https://docs.localstack.cloud/azure/services/key-vault/
• feat: CI: Add aws smoke tests #65

[j4anvii]

can i work on this?

[sanjay7178]

It takes some time , the localstack documentation is not clear

[sanjay7178]

Also when i implemented the azure in the plugin , i feel in azure portal it was too complex to get the azure credentials to setup and get working with the plugin through azure key vault

[vishwas-droid]

Hey @sanjay7178 I went through the earlier smoke test work in #20 and the AWS smoke tests added in #65 to understand how the current flow is structured.

From what I understand, the smoke tests are intentionally kept simple and bash-based so they can run both locally and in CI. Following the same approach, I’d like to extend this for the Azure Key Vault provider using LocalStack.

I noticed the same thing you mentioned — the LocalStack documentation around Azure Key Vault is not very clear, and the Azure portal credential setup can also be quite heavy just for testing. So my plan is to first experiment with the LocalStack Key Vault emulator and see what actually works reliably.

If the emulator works properly, the smoke test can follow the same simple flow used in the AWS tests: start LocalStack, create a test secret, retrieve it through the plugin using the Azure provider, and verify that the returned value matches the expected secret. I’ll also include a small JSON secret case to validate the existing azure_field extraction logic in the provider.

If this works locally, we can integrate it into the existing smoke-tests workflow so Azure runs alongside the current providers in CI, without requiring real Azure credentials or portal setup.

If it’s okay with you, I’d like to try implementing this following the same structure used in #65.

[omsherikar]

Hi @sanjay7178,

I’ve looked into the LocalStack Azure Key Vault setup. you're right the docs are a bit fuzzy, but I think I've found a clean way forward that mirrors our existing AWS smoke tests.
Can I work on it?

[sanjay7178]

Guys , as I said last time in this discussion , first we'll do the discussion , regarding the workaround to implement local stack .

Try looking into the documentation , I see might be azure localstack is similar to aws localstack , so try to have azure key vault running , so we could assure our docker plugin would work .

[sanjay7178]

Similarly we're testing 3rd party emulator for GCP secrets manager #40 (comment) (the cons are maintainer needs to do make updates to the emulator , if any breaking changes would happen to secrets manager by google cloud )