question

RazeenHendricks-7065 avatar image
0 Votes"
RazeenHendricks-7065 asked RazeenHendricks-7065 commented

ARM template with nested template holding key vault ref parameter

I’m trying to create a securestring parameter as input to credentials I want to pass to an API connection.

I’ve referenced MS Docs: Reference secrets with dynamic ID but Visual Studio 2019 complains about the “undefined” parameters used in that example. It seems that the nested template only recognizes the parameters defined in the parent template.

94278-template-error.jpg

Could you please provide or point me to a better, working example I could use to create a securestring parameter that dynamically references a key vault secret value?


azure-key-vault
template-error.jpg (218.0 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@RazeenHendricks-7065 - Welcome to Microsoft Q&A and thanks for your query.

Checking in to see if you already had a chance to review below documents related to usage of Azure Key Vault during deployment

Please see if it fits your requirement, if not please revert back with additional queries. Thanks


0 Votes 0 ·

Hi @bharathn-msft

Thank you kindly for your reply. However, you've not answered my question regarding the use of a dynamic ID as documented in your 1st link, which I also included in my question.

Those links you've supplied are for referencing secrets with a static ID, which I don't want as it means hardcoding which defeats the purpose of automation.

Please explain why the example in the documentation yields errors in Visual Studio 2019, and provide an example that works. If the example in the documentation is correct and will work in Azure DevOps, but Visual Studio is at fault with schema validation, please indicate this.

Looking forward to your reply.

0 Votes 0 ·

0 Answers