New-AzResourceGroupDeployment : needs to show Bicep error message on console #14508

shenglol · 2021-03-10T18:26:30Z

Description

The deployment cmdlet won't work if a Bicep file contains errors. I would expect it to print out the compilation errors. Also, if a Bicep file is valid but has warnings, the warnings will not be printed.

Steps to reproduce

> New-AzResourceGroupDeployment -TemplateFile .\withErrors.bicep -ResourceGroupName test
New-AzResourceGroupDeployment: Cannot retrieve the dynamic parameters for the cmdlet. The WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within the same thread. Validate that the cmdlet makes these calls correctly, or contact Microsoft Customer Support Services.

Environment data

Module versions

Name                           Value
----                           -----
PSVersion                      7.1.2
PSEdition                      Core
GitCommitId                    7.1.2
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Debug output

~\Desktop\bicep-bugbash
> $DebugPreference='Continue'

~\Desktop\bicep-bugbash
> New-AzResourceGroupDeployment -TemplateFile .\withErrors.bicep -ResourceGroupName test -Debug
New-AzResourceGroupDeployment: Cannot retrieve the dynamic parameters for the cmdlet. The WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within the same thread. Validate that the cmdlet makes these calls correctly, or contact Microsoft Customer Support Services.

Error output

DEBUG: 10:25:07 AM - ResolveError begin processing with ParameterSet 'AnyErrorParameterSet'.
DEBUG: 10:25:07 AM - using account id 'shenglol@microsoft.com'...
WARNING: Upcoming breaking changes in the cmdlet 'Resolve-AzError' :
The `Resolve-Error` alias will be removed in a future release.  Please change any scripts that use this alias to use `Resolve-AzError` instead.
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

   HistoryId: 20

Message        : Cannot retrieve the dynamic parameters for the cmdlet. The WriteObject and WriteError methods cannot
                 be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing
                 methods, and they can only be called from within the same thread. Validate that the cmdlet makes
                 these calls correctly, or contact Microsoft Customer Support Services.
StackTrace     :    at System.Management.Automation.CmdletParameterBinderController.HandleCommandLineDynamicParameters(
                 ParameterBindingException& outgoingBindingException)
                    at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidati
                 on(Collection`1 arguments)
                    at
                 System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1
                 arguments)
                    at System.Management.Automation.CommandProcessor.BindCommandLineParameters()
                    at System.Management.Automation.CommandProcessor.Prepare(IDictionary psDefaultParameterValues)
                    at System.Management.Automation.CommandProcessorBase.DoPrepare(IDictionary
                 psDefaultParameterValues)
                    at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
                    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
                 input)
                 --- End of stack trace from previous location ---
                    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
                 input)
                    at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput,
                 CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
                 commandRedirections, FunctionContext funcContext)
                    at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
                    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
                 frame)
Exception      : System.Management.Automation.ParameterBindingException
InvocationInfo : {New-AzResourceGroupDeployment}
Line           : New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -ResourceGroupName test
Position       : At line:1 char:1
                 + New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -Resour …
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 20

Message        : The WriteObject and WriteError methods cannot be called from outside the overrides of the
                 BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within
                 the same thread. Validate that the cmdlet makes these calls correctly, or contact Microsoft Customer
                 Support Services.
StackTrace     :    at System.Management.Automation.MshCommandRuntime.ThrowIfWriteNotPermitted(Boolean
                 needsToWriteToPipeline)
                    at System.Management.Automation.MshCommandRuntime.DoWriteError(Object obj)
                    at System.Management.Automation.MshCommandRuntime.WriteError(ErrorRecord errorRecord, Boolean
                 overrideInquire)
                    at System.Management.Automation.MshCommandRuntime.WriteError(ErrorRecord errorRecord)
                    at System.Management.Automation.Cmdlet.WriteError(ErrorRecord errorRecord)
                    at Microsoft.WindowsAzure.Commands.Utilities.Common.CmdletExtensions.<>c__DisplayClass14_0`1.<Execu
                 teScript>b__0(ErrorRecord e)
                    at Microsoft.WindowsAzure.Commands.Utilities.Common.GeneralUtilities.ForEach[T](IEnumerable`1
                 sequence, Action`1 action)
                    at Microsoft.WindowsAzure.Commands.Utilities.Common.CmdletExtensions.ExecuteScript[T](PSCmdlet
                 cmdlet, String contents)
                    at
                 Microsoft.Azure.Commands.ResourceManager.Cmdlets.Utilities.BicepUtility.BuildFile[T](ScriptExecutor`1
                 executeScript, String bicepTemplateFilePath)
                    at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.ResourceWithParameterCmdletBase.
                 BuildAndUseBicepTemplate()
                    at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.ResourceWithParameterCmdletBase.
                 GetDynamicParameters()
                    at Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.CmdletBase.DeploymentCreateCmdle
                 t.GetDynamicParameters()
                    at System.Management.Automation.CmdletParameterBinderController.HandleCommandLineDynamicParameters(
                 ParameterBindingException& outgoingBindingException)
Exception      : System.Management.Automation.PSInvalidOperationException
InvocationInfo : {New-AzResourceGroupDeployment}
Line           : New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -ResourceGroupName test
Position       : At line:1 char:1
                 + New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -Resour …
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 20

Message        : C:\Users\Shenglong\AppData\Local\Temp\withError.bicep(1,11) : Error BCP004: The string at this
                 location is not terminated due to an unexpected new line character.
StackTrace     :
Exception      : System.Management.Automation.RemoteException
InvocationInfo : {New-AzResourceGroupDeployment}
Line           : New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -ResourceGroupName test
Position       : At line:1 char:1
                 + New-AzResourceGroupDeployment -TemplateFile .\withError.bicep -Resour …
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 20

The text was updated successfully, but these errors were encountered:

shenglol · 2021-03-10T18:27:06Z

@BethanyZhou FYI.

dingmeng-xue · 2021-03-11T00:50:35Z

According to Azure/bicep#1757, we need to show output of Bicep on PowerShell console.

BethanyZhou · 2021-03-11T02:11:25Z

Thanks @shenglol for your information. This issue has been fixed in #14449. The Bicep error message will be thrown to console in the next release. Besides, all detailed information from Bicep will be available if -Verbose is specified. Thanks.

davidcorbin-atmosera · 2022-02-16T17:07:13Z

As of today (in a fresh environment, so everything should be up to date)... still getting the cryptic error of
New-AzDeployment: Cannot retrieve the dynamic parameters for the cmdlet. Cannot find path 'C:\Users\David.Corbin\AppData\Local\Temp\59950199-84c1-4b09-ac62-c8a015a13fc9\Create-Infrastructure.json' because it does not exist.
under various error conditions...

BethanyZhou · 2022-02-17T02:04:44Z

Thanks for reporting @dcorbin-wintellect . What's your Az.Resources version. Please try to get that by Get-Module

davidcorbin-atmosera · 2022-02-17T11:22:09Z

PS D:\Data-Lakes-Factories-Bricks> Get-Module Az.Resources ModuleType Version PreRelease Name ExportedCommands ---------- ------- ---------- ---- ---------------- Script 5.3.0 Az.Resources {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Get-AzDeployment…} ***@***.*** ***@***.*** From: Beisi Zhou ***@***.***> Sent: Wednesday, February 16, 2022 9:05 PM To: Azure/azure-powershell ***@***.***> Cc: David Corbin ***@***.***>; Mention ***@***.***> Subject: Re: [Azure/azure-powershell] New-AzResourceGroupDeployment : needs to show Bicep error message on console (#14508) Thanks for reporting @dcorbin-wintellect<https://github.com/dcorbin-wintellect> . What's your Az.Resources version. Please try to get that by Get-Module — Reply to this email directly, view it on GitHub<#14508 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3Q5VDIQKGU4ZWCOK7UHVLU3RJUPANCNFSM4Y6TQNGA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

BethanyZhou · 2022-02-21T03:01:48Z

Thanks for your help. @dcorbin-wintellect

Do you mind providing your bicep version by running bicep --version in powershell console?
Could you reproduce your issue and turn on Verbose and Debug? Like following command New-AzDeployment -TemplateFile test.bicep -ResourceGroup xxx-rg -Verbose -Debug. It will provide more information.

davidcorbin-atmosera · 2022-02-21T10:44:33Z

@BethanyZhou -- It was an old install of bicep .... Had not realized that "c:>bicep" and "c:>az bicep" invoked completely different installations...

BethanyZhou · 2022-02-22T01:44:36Z

Ok, could you run your command with -Verbose -Debug to show us more information?

davidcorbin-atmosera · 2022-02-22T11:42:47Z

@BethanyZhou - The machine has since been updated.

shenglol added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Mar 10, 2021

shenglol mentioned this issue Mar 10, 2021

New-AzResourceGroupDeployment : Cannot retrieve the dynamic parameters for the cmdlet. Azure/bicep#1757

Closed

dingmeng-xue changed the title ~~New-AzResourceGroupDeployment : Cannot retrieve the dynamic parameters for the cmdlet with a Bicep file has errors.~~ New-AzResourceGroupDeployment : needs to show Bicep error message on console Mar 11, 2021

dingmeng-xue added ARM feature-request This issue requires a new behavior in the product in order be resolved. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Mar 11, 2021

dingmeng-xue added this to the S184 (2021-03-23) milestone Mar 11, 2021

dingmeng-xue assigned BethanyZhou Mar 11, 2021

BethanyZhou linked a pull request Mar 11, 2021 that will close this issue

[Az.Resources] Redirect bicep message to verbose stream #14449

Merged

8 tasks

BethanyZhou closed this as completed Mar 11, 2021

brwilkinson mentioned this issue Jun 9, 2021

AzurePowerShellV5 task cannot find bicep from path, bicep related commands are failing microsoft/azure-pipelines-tasks#14934

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

New-AzResourceGroupDeployment : needs to show Bicep error message on console #14508

New-AzResourceGroupDeployment : needs to show Bicep error message on console #14508

shenglol commented Mar 10, 2021

shenglol commented Mar 10, 2021

dingmeng-xue commented Mar 11, 2021

BethanyZhou commented Mar 11, 2021

davidcorbin-atmosera commented Feb 16, 2022

BethanyZhou commented Feb 17, 2022

davidcorbin-atmosera commented Feb 17, 2022 via email

BethanyZhou commented Feb 21, 2022

davidcorbin-atmosera commented Feb 21, 2022

BethanyZhou commented Feb 22, 2022

davidcorbin-atmosera commented Feb 22, 2022

New-AzResourceGroupDeployment : needs to show Bicep error message on console #14508

New-AzResourceGroupDeployment : needs to show Bicep error message on console #14508

Comments

shenglol commented Mar 10, 2021

Description

Steps to reproduce

Environment data

Module versions

Debug output

Error output

shenglol commented Mar 10, 2021

dingmeng-xue commented Mar 11, 2021

BethanyZhou commented Mar 11, 2021

davidcorbin-atmosera commented Feb 16, 2022

BethanyZhou commented Feb 17, 2022

davidcorbin-atmosera commented Feb 17, 2022 via email

BethanyZhou commented Feb 21, 2022

davidcorbin-atmosera commented Feb 21, 2022

BethanyZhou commented Feb 22, 2022

davidcorbin-atmosera commented Feb 22, 2022