Skip to content
Artificial intelligence. Clearly. RSS feed
AI NEWS AI

News. Evidence. Perspective.

Terraform opens an infrastructure catalogue to developers and AI agents

A new portal packages reusable infrastructure as templates and add-ons. A separate search preview helps teams bring existing cloud resources into the same management system.

HashiCorp’s Terraform Developer Portal puts a catalogue of approved infrastructure inside HCP Terraform. Its 27 October introduction describes the same templates being available to developers and AI agents. The portal is in public preview; its documentation advises against production use during the beta.[1][2]

Platform teams turn reusable Terraform modules into templates with specified inputs. A developer can request an application, then attach an approved add-on such as a database or cache. The new interface gives those components names and relationships that an application team can work with.[1][2]

Terraform’s underlying job is to turn a description of desired infrastructure into operations. It compares configuration with existing resources, prepares a plan and applies the accepted changes in dependency order. A database, network and application server can therefore be managed as related parts of a system rather than separate provisioning instructions.[4]

The portal’s launch account illustrates an agent finding the appropriate template, identifying the required inputs and initiating that existing provisioning workflow. It can also retrieve application context and the outcome of a run. The platform team still designs the catalogue; the agent helps a developer use it.[1]

Bring the existing estate into the picture

An additional public preview, announced in IBM’s 26 October update, addresses resources created outside Terraform. Enhanced search combines an interactive discovery interface with policy evaluation before import. Compliant resources can proceed into management; others are flagged for remediation.[3]

Import begins with the identity of an existing resource: an AWS storage bucket, for example. Terraform records that resource at a particular address in its state, with a matching configuration block describing it. The bucket remains where it is, while Terraform gains the information it needs to plan and manage subsequent changes.[5]

Follow the evidence

Sources & further reading

  1. What is Terraform Developer Portal? HashiCorp documentation · Accessed 28 Oct 2026
  2. What is Terraform? HashiCorp documentation · Accessed 28 Oct 2026
  3. Import resources overview HashiCorp documentation · Accessed 28 Oct 2026