Mis-diagnosed terraform_remote_state datasource

[radeksimko]

Another example with terraform_remote_state datasource if it's helpful:

Originally posted by @brettcurtis in #1573 (comment)

---

data "terraform_remote_state" "foo" {
  backend = "gcs"
  config = {
    bucket = "value"
  }

  workspace = "foo"
}

[radeksimko]

This appears to be related to how we assemble the dependent schema for terraform_remote_state. I managed to find a snippet which does not fail the validation:

data "terraform_remote_state" "foo" {
  backend   = ""
  provider  = terraform
  workspace = "foo"
}

[radeksimko]

This is related to hashicorp/terraform-schema#251 - it appears we did not account for all edge cases there.

[radeksimko]

I found a solution in hashicorp/terraform-schema#272 which is now pending review.

I will post updates here when we merge it and release it (hopefully soon).

[radeksimko]

A new version 2.28.1 was just released. This fixes the reported bug. The update should appear automatically in VS Code.

Thank you for the the report @brettcurtis

---

In case you experience any different validation related bug, please do let us know through a new issue.

[github-actions]

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.