Skip to content
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

Template is recognized and reports no problems until Select ParameterFile. #782

Closed
Falconwmua opened this issue Jun 11, 2020 · 3 comments
Closed

Comments

@Falconwmua
Copy link

Does this occur consistently? Yes
Repro steps:

  1. Open template file
  2. Wait for VSCode to recognize it as a Azure Resource Manager Template
  • ARM Template Outline populates, file type and icon change
  1. Go to Parameters section of template, right click to "Select/Create Parameter File..."
  2. 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

Call Stack
Object.<anonymous> extension.bundle.js:1:596601
fulfilled extension.bundle.js:1:593686
@StephenWeatherford
Copy link
Contributor

@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.

@Falconwmua
Copy link
Author

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.

@StephenWeatherford
Copy link
Contributor

I just deployed one with no problems.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants