Parameter file validation fails with: Unable to load schema from <snip> unexpected end of file.

Hi,

I automatically generated my first parameter file today via this extension (having previously been passing data via a custom PSObject) but VSCode lists the following problem:

Unable to load schema from 'https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#': unexpected end of file. (768) [2, 16]

The JSON referenced is valid, which is odd.

I’m also suffering problems in the main template file with apiVersions when they’re roughly 2021 onwards (“for full schema validation, consider updating the value to…”) but I think you’re tracking this already.

Any ideas? Thanks!

[StephenWeatherford]

Turns out it’s a vscode in version 1.63.0: https://github.com/microsoft/vscode/issues/140227. It’s been fixed in the Insiders version 1.64, if you don’t mind installing vscode insiders (https://code.visualstudio.com/insiders/)

[StephenWeatherford]

Sorry, misread your statement about schemas. We’ll be releasing a new version with updated schemas very soon (for template files, we snapshot the schemas to avoid various issues). That should hopefully help with that.

For parameter files, we rely mostly on vscode’s built-in JSON support, so we don’t have any control over the parameters file schema loading. I’m not seeing the problem myself. It could be a CDN issue that will eventually resolve itself, we’ve seen those before. I would try F1 and “JSON: Clear schema cache”.

If that doesn’t work, I’m guessing there’s not much that actually not working, right? Our functionality (param snippets etc) doesn’t depend on the schema loading.