GoLand adds Terraform Stacks

Infrastructure code is the text file version of a cloud control panel: instead of clicking buttons to make a database or a network, you write the desired setup and let a tool build it. Terraform is one of the biggest tools for that job, and JetBrains just taught its GoLand editor to understand Terraform Stacks directly inside the same window where Go developers write application code. (jetbrains.com) A Stack is HashiCorp’s way to group several infrastructure pieces that belong together, like treating the database, network, and app servers as one kit instead of three loose boxes. HashiCorp says each Stack is split into components, and each component points to a Terraform module that defines one part of the system. (developer.hashicorp.com, developer.hashicorp.com) HashiCorp also separates the blueprint from the rollout. A `.tfstack.hcl` file defines the shared structure, while a `.tfdeploy.hcl` file defines where that structure gets deployed, such as a development environment, a production account, or a specific cloud region. (developer.hashicorp.com, developer.hashicorp.com) That model is useful when one company runs the same setup in several places. HashiCorp’s docs describe Stacks as a way to repeat infrastructure across multiple environments, regions, and accounts while managing the whole group as a unit in HashiCorp Cloud Platform Terraform. (developer.hashicorp.com, developer.hashicorp.com) Until now, a Go developer working in a monorepo often had one tool for Go files and another tool or browser tab for infrastructure files. GoLand 2026.1 adds Stack-aware navigation so the editor can show the infrastructure structure, jump between components, and help create new deployments without leaving the integrated development environment. (jetbrains.com, jetbrains.com) JetBrains says the editor now supports both Terraform workspaces and Terraform Stacks, which matters because those are two different ways to organize infrastructure. In the Stack view, developers can inspect components and resources from inside GoLand instead of treating the infrastructure directory like plain text. (jetbrains.com, developer.hashicorp.com) The practical gain is speed on small tasks that used to break concentration. If a backend engineer changes a Go service and also needs to add a matching deployment, GoLand can now offer code completion, better navigation, and Stack creation tools in the same editor session. (jetbrains.com, jetbrains.com) This also lines up with how Terraform Stacks are meant to be operated. HashiCorp’s command line now has a dedicated `terraform stacks` command family for initializing, validating, and managing Stack configurations and deployments, so editor support is arriving as the feature itself becomes more formalized in the Terraform workflow. (developer.hashicorp.com) GoLand 2026.1 was released on March 26, 2026, and JetBrains lists Terraform Stack support as one of the release’s DevOps features. That puts infrastructure work closer to ordinary application work for teams that already live in GoLand and keep app code and cloud code in the same repository. (jetbrains.com, jetbrains.com)