I will say I've had a lot of success with AI and boiler plate HCL.
I try to avoid modules out of the gate until I know the shape of a system and the lifecycles of things and I've been pleasantly surprised with how well the AI agents get AWS things correct out of the gate with HCL.
This should super charge this workflow since it should be able to pull out the provider docs / code for the specific version in use from the lockfile.
throwup238 · 3h ago
Does anyone know of an MCP server like this that can work with Terragrunt?
d_watt · 3h ago
I'd think this would work, as the 4 tools listed are about retrieving information to give agents more context of correct providers and modules. Given terragrunt works with terraform directly, I'd think that it would help with it as well, just add rules/prompts that are explicit about the code being generated being in terra grunt file structure / with terragrunt commands.
notpushkin · 36m ago
And it’s MPL, so you’re free to use it with OpenTofu as well (even if competing with Hashicorp).
But as mdaniel notes in a sibling thread, this doesn’t seem to do much at this point.
tecleandor · 3h ago
Oh, just what I needed to raise my RUMs and send my Hashicorp bill through the roof!
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
I try to avoid modules out of the gate until I know the shape of a system and the lifecycles of things and I've been pleasantly surprised with how well the AI agents get AWS things correct out of the gate with HCL.
This should super charge this workflow since it should be able to pull out the provider docs / code for the specific version in use from the lockfile.
But as mdaniel notes in a sibling thread, this doesn’t seem to do much at this point.
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