VS Code -> HCP Terraform error: Failed to fetch organizations - Response validation failed

[justinclayton]

Extension Version

v2.32.3

VS Code Version

Version: 1.93.0
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z (6 days ago)
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.5.0

Operating System

macOS Sonoma 14.5 (23F79)

Terraform Version

Terraform v1.8.4 on darwin_arm64

Steps to Reproduce

1. Perform successful auth login (supply token)
2. Refresh organizations

Expected Behavior

Get returned a list of organizations so I can use the extension sidebar

Actual Behavior

The above error in the title.

Terraform Configuration

No response

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

[jpogran]

Hi @justinclayton, thanks for reporting this issue. This type of error usually means either the token used did not have permission to enumerate organizations, or the response returned was not in the shape we expected.

Assuming the token you used does have the correct permissions, can you try to login again and open the 'HashiCorp Terraform' output channel and paste the redacted content here? Or email me at james dot pogran at hashicorp dot com? The full error will be logged there and that will help us figure things out.

[github-actions]

Marking this issue as stale due to inactivity over the last 30 days. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

Thank you for understanding.

[github-actions]

Closing this issue due to its staleness.

If the issue was automatically closed and you feel it should be reopened, we encourage creating a new one linking back to this one for added context.

Thank you!

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