Error in transit_encryption_mode attribute on AWS aws_elasticache_replication_group Resource

[webgene]

Extension Version

v2.30.1

VS Code Version

Version: 1.89.1 Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685 Date: 2024-05-07T05:14:32.757Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 23.5.0

Operating System

macOS Sonoma Version 14.5 (23F79)

Terraform Version

Terraform v1.8.3 on darwin_arm64

Steps to Reproduce

1. Add transit_encryption_mode = "preferred" in aws_elasticache_replication_group resouce.

Expected Behavior

transit_encryption_mode Attribute added in latest version of terraform AWS provider, hence it shouldn't show any error for this attribute.

Actual Behavior

[

](url)

Terraform Configuration

resource "aws_elasticache_replication_group" "default" {
 ......
  transit_encryption_enabled = true
  transit_encryption_mode    = "preferred"
.....
}

Project Structure

No response

Gist

No response

Anything Else?

No response

Workarounds

No response

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

[dbanck]

Hi @webgene, thanks for the report.

We bundle the latest provider schema available at the time of the language server and extension release. If new attributes, blocks or resources are introduced since then, we can't automatically reflect them (yet). The next language server release will bundle the updated schema and fix the problem. We apologize for the inconvenience.

In the meantime, when you run terraform init, we'll use the appropriate provider schema from disk.

[dbanck]

@webgene We have released a new version 2.30.2. This updates the schema to the latest version and should fix the validation error. The update should show up automatically in VS Code.

---

If you experience any other validation related bug, please let us know via a new issue.

[github-actions[bot]]

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.