You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wait for VSCode to recognize it as a Azure Resource Manager Template
ARM Template Outline populates, file type and icon change
Go to Parameters section of template, right click to "Select/Create Parameter File..."
VSCode returns notification or error below instead of prompting for parameter file.
Action: azurerm-vscode-tools.selectParameterFile
Error type: Error
Error Message: "c:\repos\allspice\aspice-armt-partner-env-platformfabric\PlatformFabric.json" does not appear to be an Azure Resource Manager deployment template file.
Version: 0.10.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.46.0
Language: en
@Falconwmua Thanks for taking the time to report this issue! Could you check to see if your template file is saved as UTF-8 with BOM? And if so, consider resaving without the BOM (F1 -> Change File Encoding)? There was a known issue with that which will be fixed in the next release (see #721).
If you need it saved with the BOM, I believe you can change it back after setting up the parameter file association.
That fixed it. I thought I searched but guess not well enough. Was there a related issue with some of the other tooling (CLI/PowerShell) with regards to the UTF-8 with BOM? An engineer brought this up a while back but we couldn't reproduce it and he had upgraded and changed all the files that had the problem.
Does this occur consistently? Yes
Repro steps:
Action: azurerm-vscode-tools.selectParameterFile
Error type: Error
Error Message: "c:\repos\allspice\aspice-armt-partner-env-platformfabric\PlatformFabric.json" does not appear to be an Azure Resource Manager deployment template file.
Version: 0.10.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.46.0
Language: en
Call Stack
The text was updated successfully, but these errors were encountered: