add Azure Key Vault service doc

[HarshCasper]

Resolves DOC-76

[cloudflare-workers-and-pages]

Deploying localstack-docs with    Cloudflare Pages

Latest commit:	745de87
Status:	✅  Deploy successful!
Preview URL:	https://59f87855.localstack-docs.pages.dev
Branch Preview URL:	https://harshmishra-doc-76.localstack-docs.pages.dev

View logs

[paolosalvatori]

Thanks Harsh, I'm adding @bryansan-local as an additional reviewer as he created the emulator for Azure Key Vault. It looks good to me. Maybe we could extend the documentation to show how to:

• Update a secret
• Peek a specific secret version
• Delete a secret
• Create a certificate
• Read a certificate
• Etc.

Please check my comments. and additions. I approve it the PR but it would be great if you could include suggested content and make the necessary edits and additions. cc: @lazarkanelov

Question for Bryan: does LocalStack for Azure uses any environment variable to customize the behavior of Azure Key Vault emulator? Any constraints to add in a specific section?

[paolosalvatori]

Suggested change

	Key Vault also supports secure key management and certificate lifecycle operations.
	Key Vault also supports secure key management and certificate lifecycle operations. For more information, see [About Azure Key Vault](https://learn.microsoft.com/en-us/azure/key-vault/general/overview).

[paolosalvatori]

Suggested change

	LocalStack for Azure allows you to build and test Key Vault workflows in your local environment.
	LocalStack for Azure provides a local environment for building and testing applications that make use of Azure Key Vault.

[paolosalvatori]

I would also add a reference to the following sample which makes use of Azure Key Vault. Now the repo is still private, but we plan to flip it to public when we go live:

• Azure Web App with Azure SQL Database and Azure Key Vault

[paolosalvatori]

@bryansan-local can you please review this article and provide your notes and suggestions? For example, does the emulator make use of environment variables to customize the behavior of the Key Vault emulator? What are the main limitations and constraints with respect to Key Vault on Azure? Thanks!

[bryansan]

Question for Bryan: does LocalStack for Azure uses any environment variable to customize the behavior of Azure Key Vault emulator? Any constraints to add in a specific section?

No, it doesn't use any environment variables to customize behaviors. The only limitation I know of is not supporting keys or any HSM-related operations or operations related to getting a real certificate from an official CA.

Thanks Harsh, I'm adding @bryansan-local as an additional reviewer as he created the emulator for Azure Key Vault. It looks good to me. Maybe we could extend the documentation to show how to:

• Update a secret
• Peek a specific secret version
• Delete a secret
• Create a certificate
• Read a certificate
• Etc.

Do you really think we should include sample code for all these operations? In my opinion people can already use without any changes the documentation and samples of the client SDK they are using so we don't really have to duplicate it nor maintain it. Thoughts @DrisDary, @lazarkanelov, @alexlave100, @bblommers?

@paolosalvatori will we add a list of all the operations we support like we had in the old docs? That was pretty useful

[bryansan]

@paolosalvatori will we add a list of all the operations we support like we had in the old docs? That was pretty useful

Is this bit by any chance? <AzureFeatureCoverage service="Microsoft.KeyVault" client:load />

[bryansan]

I would add a bit here showing this to close the loop.

azlocal stop_interception

[bblommers]

Do you really think we should include sample code for all these operations? In my opinion people can already use without any changes the documentation and samples of the client SDK they are using

I think it's worth keeping, for two reasons:

• People might not be familiar with Azure (or the Azure SDK docs)
• People might not immediately understand how LocalStack works. Showing them that they can use the az CLI like normal, without any changes, really shows the purpose of LocalStack, and how easy it is to use

Is this bit by any chance? <AzureFeatureCoverage service="Microsoft.KeyVault" client:load />

Yes, that's the bit that loads the table with all supported services. The first comment has a link to a preview where you can see how it looks. This is the direct link to the KeyVault page: https://59f87855.localstack-docs.pages.dev/azure/services/key-vault/

[DrisDary]

Do you really think we should include sample code for all these operations? In my opinion people can already use without any changes the documentation and samples of the client SDK they are using so we don't really have to duplicate it nor maintain it. Thoughts @DrisDary, @lazarkanelov, @alexlave100, @bblommers?

I think in general we should because as @bblommers rightfully said its good for people who need to understand how certificates are used.