Parameters in Nested Templates is broken
For nested templates, you cannot use parameters or variables that are defined within the nested template. It is currently broken (as per the documentation).
It'd be great if this could be fixed. An example of what I'm talking about can be seen here:
https://github.com/bmoore-msft/AzureRM-Samples/blob/master/dynamicSecretId/azuredeploy.inline.json
Note: It's not only with Keyvault references that this is broken, but rather all inline parameters when using an inline template.
Thanks!
Anonymous
shared this idea
Thank you for taking the time to vote for this item.
This is something we plan to address.
5 comments
-
Oskar Stucki
commented
I guess still no update...
-
Fraser
commented
Is there an ETA on this? Also require this for the same reasons as everyone else
-
Joe
commented
It is still broken. Can you please explain your scope mapping?
-
Jeff Dahan
commented
I am also having this issue. Is there an ETA for this? I am working with a customer who deploys many environments programmatically and hard coding anything breaks our value proposition. Also, keeping the nested templates in a storage account makes things tough for them.
-
[Deleted User]
commented
Another use case: Pushing an array with > 1 item, from outputs/references into a copy loop.
Currently you cannot use an expresison like "[length(reference('deployedResource').arrayProperty)]" in the 'count' property of a copy loop - even in a nested template.