arm-estimator: v1.5 fails with template error but previous versions work
Hey Kamil,
When trying to use the latest release, I get an error:
What If status:
-> Cache miss for What If data.
-> Waiting for response from What If API.
-> Saving What If response to cache.
[Error] An error happened when performing WhatIf operation.
[Error] {
"code": "InvalidTemplate",
"message": "Deployment template validation failed: \u0027The value for the template parameter \u0027resourceLocation\u0027 at line \u00271\u0027 and column \u0027180\u0027 is not provided. Please see https://aka.ms/arm-create-parameter-file for usage details.\u0027.",
"details": null
}
Unhandled exception: System.Exception: An error happened when performing WhatIf operation.
at ACE.Program.<>c.<<Main>b__2_1>d.MoveNext() in /home/runner/work/arm-estimator/arm-estimator/ace/Program.cs:line 139
--- End of stack trace from previous location ---
at System.CommandLine.Invocation.AnonymousCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.AnonymousCommandHandler.SyncUsingAsync(InvocationContext context)
at System.CommandLine.Invocation.AnonymousCommandHandler.Invoke(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()
However, what is interesting, is that if I roll back my task to v1.5-beta2 or any previous version, and rerun the pipeline task - it will be fine.
The templates it is scanning against are the same. I have also verified I can run a manual what-if in my CLI terminal OK for these also, and it is successful.
Let me know if you need any other info!
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (9 by maintainers)
Commits related to this issue
- test: :test_tube: Added test confirming problem with Bicep CLI parameters compilation (#271) — committed to TheCloudTheory/arm-estimator by kamil-mrzyglod 2 years ago
@riosengineer
--generate-markdown-outputand--markdown-output-filename, I’ll add them to the Wiki soon.@riosengineer I think I managed to reproduce the error. It seems it’s caused by Bicep CLI compilation which generates different schema for parameters than Azure CLI. I’ll check what kind of workaround or fix will mitigate the issue for you.