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
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
The text was updated successfully, but these errors were encountered:
@tomburge We just released a new version 2.29.4. This updates the schema to the latest version and should fix the validation error. The update should appear automatically in VS Code.
In case you experience any different validation related bug, please do let us know through a new issue.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Extension Version
v2.29.3
VS Code Version
Version: 1.86.0 (system setup)
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:28:19.990Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.19045
Operating System
Windows 10 Pro 22H2 19045.3996
Terraform Version
Terraform v1.6.2 on windows_amd64
Steps to Reproduce
Expected Behavior
VS Code shouldn't have a warning for a supported attribute in Terraform.
Actual Behavior
VS Code gives a warning for an unsupported attribute in Terraform.
Terraform deploys successfully with the kms_key_id attribute.
Terraform Configuration
No response
Project Structure
No response
Gist
No response
Anything Else?
No response
Workarounds
None
References
Help Wanted
Community Note
The text was updated successfully, but these errors were encountered: