hashicorp / vscode-terraform

HashiCorp Terraform VSCode extension
https://marketplace.visualstudio.com/items?itemName=HashiCorp.terraform
Mozilla Public License 2.0
924 stars 179 forks source link

Unexpected Attribute kms_key_id in aws_codecommit_repository resource #1686

Closed tomburge closed 8 months ago

tomburge commented 8 months ago

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

  1. Open vscode
  2. Create a file named vpc.tf
  3. Configure as follows:
    resource "aws_codecommit_repository" "repository" {
    repository_name = var.name
    default_branch  = var.default_branch
    description     = var.description
    kms_key_id      = var.kms_key_arn
    tags            = var.tags
    }
  4. Install and enable the official Hashicorp terraform for visual studio code.

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

asychev commented 8 months ago

Should be https://github.com/hashicorp/vscode-terraform/issues/1681

dbanck commented 8 months ago

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

github-actions[bot] commented 7 months ago

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.