Syntax Highlighting tied to version constraints in local workspace.

[plieberg]

Extension Version

v2.32.3

Problem Statement

Syntax highlighting and validation are great, but it appears to always assume the latest version of the provider. In my case, the azurerm provider, which recently released v4.x. We are not ready (haven't had time) to upgrade all of our modules to this version and it is now highlighting invalid options on certain resources for v4 of the provider when we are running v3 and those options are still valid.

Expected User Experience

It would be nice to tie the syntax highlighting and validation to the version constraint specified in the current workspace.

Proposal

Check the local workspace/folder for version constraints and adjust syntax highlighting and validation to match the latest version of the provider allowed by those constraints.

References

No response

Help Wanted

• [ ] I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[plieberg]

Another option would be to allow the user to set version constraints in the plug-in settings.