-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What-If and conditional deployment #223
Comments
On the same lines, it feels like resources showing a |
Can you clarify what were you expecting to see? Can you share the output of the what-if response and what in the response looks incorrect?
resources with a dependsOn property should not be ignored. We have #157 related to nested deployments. Could it be related to that? |
See the
Thanks for linking to it, it might well be! I cannot promise to look into this right now but that's a good starting point. |
Describe the noise
Resource type (i.e. Microsoft.Storage/storageAccounts): any
apiVersion: n/a
Client (PowerShell, Azure CLI, or API): PowerShell
Relevant ARM Template code (we only need the resource object for the above
resourceType
andapiVersion
, but if it's easier you can include the entire template:Expected response (i.e. "I expected no noise since the template has not been modified since the resources were deployed): the default parameter value is
1
and it is not overridden, so I expect to see updation information for this ADF instance too.Current (noisy) response (either include a screenshot of the what-if output, or copy/paste the text): n/a
Additional context: the command we use is
New-AzResourceGroupDeployment -ResourceGroupName ??? -TemplateFile azuredeploy_world.json -TemplateParameterFile azuredeploy_world_params.json -Whatif -WhatIfResultFormat FullResourcePayloads
Not sure if this is noise, expected behavior or just unsupported. Apologies in advanced if we missed any information in this sense, please gently point to the relevant docs.
Thank you,
The text was updated successfully, but these errors were encountered: