Skip to content

fix: pin terraform-mcp-server Docker image to explicit version tag#57

Open
xiaolai wants to merge 1 commit intohashicorp:mainfrom
xiaolai:fix/nlpm-pin-mcp-server-image
Open

fix: pin terraform-mcp-server Docker image to explicit version tag#57
xiaolai wants to merge 1 commit intohashicorp:mainfrom
xiaolai:fix/nlpm-pin-mcp-server-image

Conversation

@xiaolai
Copy link
Copy Markdown

@xiaolai xiaolai commented Apr 6, 2026

Automated audit: This PR was generated by NLPM, a natural language programming linter, running via claude-code-action. Please evaluate the diff on its merits.

Bug

Both terraform/code-generation/.claude-plugin/plugin.json and terraform/module-generation/.claude-plugin/plugin.json reference the MCP server image as hashicorp/terraform-mcp-server without a version tag. Docker resolves untagged references to latest, which means:

  • The image pulled can change silently between installs, making setups non-reproducible.
  • Users have no auditable record of which version of the MCP server they are running alongside sensitive credentials (TFE_TOKEN).
  • A supply-chain compromise of the latest tag would affect all users without warning.

Fix

Pin both plugin manifests to the current stable release tag 0.5.0:

- "hashicorp/terraform-mcp-server"
+ "hashicorp/terraform-mcp-server:0.5.0"

The 0.5.0 tag was confirmed from the terraform-mcp-server releases. When a newer version is released, the tag can be intentionally bumped in a deliberate commit.

Why it matters

This image receives TFE_TOKEN — a Terraform Enterprise API credential. Pinning to an explicit version ensures users can verify exactly what runs with that credential, and prevents unexpected breakage when latest advances.

Both terraform plugin manifests referenced `hashicorp/terraform-mcp-server`
without a version tag, which silently pulls `latest` and makes the setup
non-reproducible. Pin to `0.5.0` (current stable release) so users get
a consistent, auditable image.

Co-Authored-By: Claude Code <[email protected]>
@xiaolai xiaolai requested a review from a team as a code owner April 6, 2026 11:58
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

1 similar comment
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant