4 ms·
Oh, just what I needed to raise my RUMs and send my Hashicorp bill through the roof!
by tecleandor 1y ago
Oh, just what I needed to raise my RUMs and send my Hashicorp bill through the roof!
- mdaniel 1y agoI didn't downvote you, but this thing is actually back to their MPL-2 roots (for now!) and I don't see any references to github.com/hashicorp/terraform in https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.0/go.mod https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.... and I would guess patching https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.0/pkg/hashicorp/tfregistry/utils.go#L422 https://github.com/hashicorp/terraform-mcp-server/blob/v0.1.... to accept an env-var or config flag or whatever would decouple it from their centralization The back side of that coin is that it similarly just(?) seems to be a fancy way of feeding the terraform provider docs to the LLM, which was already available via `tofu provider schema -json` without all this http business. IMHO the fields in the provider binary that don't have populated "description" fields are a bug
- benterix 1y ago> Oh, just what I needed to raise my RUMs and send my Hashicorp bill through the roof! out of curiosity, what are you paying them for? most orgs that use tf dont
- tecleandor 1y agoNothing for, really, we were forced to. The company I work for got acquired by a way bigger company that was using tf cloud already, and they forced us in. It took two years of raging price increases from Hashicorp until we convinced them to move to Spacelift. Hashicorp, even after huge discounts, wanted around 200-300K a year (I think the original offer was like 400 or 500k). Spacelift is around 60-80K, I think, and we have more features, more runners, they fail less, and everyone is happier.