Open quality-leftovers opened 4 years ago
We don't do it today because today in ARM template deployments, outputs are only calculated at the end of a deployment. That being said, this is definitely an enhancement we would like to do, and it's on our backlog, but the work is not scheduled.
Thanks for the answer. Really linking WhatIf so far =)
@alex-frankel Is there any update on the status of this enhancement request for output values? This is one of our last gaps between using Az.Resources 1.6.0 Test-AzResourceGroupDeployment results (last version before Microsoft.Resources/deployments validate API was updated to version 2019-01-01 and started returning only resourceIds) and WhatIf deployment results.
No update.
However, what output are you seeing with the Test-Az*Deployment
cmdlet that is not show in what-if? The Test (validate) API is not capable of calculating outputs either. What-if uses the validate API under the covers prior to doing the diff, so anything shown with the Test-* cmdlet should also be able to shown in what-if.
I see I was mistaken. I checked and you are correct that outputs are not returned from earlier versions of the validate API.
Has there been any progress on this over the past 3 years?
Hello,
Are you planning to support returning (simple) output values? E.g. a string generated using: concat('mystore', uniqueString(subscription().subscriptionId, resourceGroup().id)) ?
Could not find any documentation on output values +WhatIf so far.
Kind Regards, Michael