Last year, we introduced Terraform actions and outlined our vision for deeper integration between Terraform and Ansible. As organizations increasingly rely on hybrid and multi-cloud environments, infrastructure teams need automation that spans the entire infrastructure lifecycle — from Day 0 provisioning to Day 1 configuration management, to ongoing Day 2 operations.
Our goal has been simple: Reduce operational complexity by helping Terraform and Ansible work together more seamlessly. Today, Terraform and Ansible users can already benefit from a growing set of integrations, including:
Terraform actions, enabling operational workflows and event-driven automation directly from Terraform.
The official AAP provider for Terraform, allowing organizations to manage Ansible Automation Platform resources through infrastructure as code.
The Terraform Ansible collection, enabling Ansible users to manage Terraform projects, workspaces, and runs from within Ansible Automation Platform.
Together, these capabilities have made significant progress toward bidirectional integration between Terraform and Ansible. Building on these efforts, we are excited to highlight the next phase of our continued investment with the Terraform Ansible collection 2.0 powered by pyTFE, dynamic inventory, and an enhanced Terraform actions experience.
»Terraform Ansible collection 2.0, powered by pyTFE
As infrastructure environments grow more complex, teams using Terraform and Ansible together often find themselves maintaining custom scripts, CLI wrappers, and brittle glue code just to keep the two tools in sync. These integrations can become difficult to maintain over time, break during upgrades, and create governance challenges through disconnected permission models.
To help address these challenges, we're excited to introduce the Terraform Ansible collection 2.0, powered by pyTFE.
Terraform Ansible collection 2.0 provides an API-first way to manage Terraform workflows directly from Ansible. Teams can manage workspaces and runs, leverage remote execution, access Terraform outputs, and incorporate Terraform operations into existing Ansible playbooks while maintaining governance through modern role-based access controls.
By eliminating the need for custom glue code, the collection helps reduce maintenance overhead, improve reliability, and simplify how teams integrate Terraform into broader automation workflows.
»pyTFE 1.0 reaches GA
Alongside the collection, we're also announcing the general availability of pyTFE 1.0, the official Python SDK for HCP Terraform and Terraform Enterprise.
pyTFE provides broad API coverage across Terraform workflows, including projects, workspaces, runs, tasks, teams, users, and state management capabilities. For teams that have historically maintained custom API clients or one-off Python scripts to interact with Terraform, pyTFE replaces that burden with a stable, supported SDK foundation. With this, developers and platform teams can build integrations and automation using Python without maintaining custom API clients.
The official Ansible collection is powered by pyTFE, providing a consistent and reliable foundation for Terraform automation within Ansible. Together, these releases represent another step in our continued investment in Terraform and Ansible interoperability, making it easier for organizations to automate infrastructure workflows using supported, enterprise-ready integrations.
»Progress toward dynamic inventory
Traditionally, keeping Ansible inventory synchronized with Terraform-managed infrastructure required custom scripts or other operational workarounds. When Terraform provisions a new resource, Ansible is not automatically aware of those changes — forcing teams to either write custom inventory scripts, run manual reconciliation steps, or accept some degree of drift between what Terraform knows and what Ansible sees.
To help close this gap, we're introducing an experimental dynamic inventory plugin as part of the Ansible collection 2.0, and are actively seeking customer feedback as we continue to evolve this capability.
The tfc_inv.py plugin retrieves the latest Terraform state version directly from HCP Terraform using pyTFE, parses Terraform-managed resources, and automatically generates Ansible inventory without requiring Terraform CLI access or backend credentials.
By enabling Ansible to discover Terraform-managed infrastructure directly through HCP Terraform, teams can reduce reliance on custom scripts, improve inventory consistency, and further simplify the transition from Day 0 provisioning to Day 1 configuration management.
»Dedicated actions experience
Terraform actions introduced a new way to perform Day 2 operations directly from Terraform. Whether scaling infrastructure, triggering operational workflows, or performing remediation tasks, actions help teams respond to issues without modifying infrastructure configuration.
To make these workflows easier to discover and manage, we're introducing a dedicated actions experience in HCP Terraform. The new actions page provides a centralized location to view available actions, invoke them directly from the UI, and review the results of previous invocations. Teams can quickly see what actions are available within a workspace, when they were last executed, how they were triggered, and the outcome of those operations.
For Terraform and Ansible users, this provides better visibility into operational workflows that extend beyond provisioning. Teams can more easily track Terraform-triggered Ansible automations, understand what remediation actions have been performed, and quickly access approved operational workflows when issues arise.
By bringing action discovery, invocation, and history into a single experience, we're continuing to help teams bridge the gap between infrastructure provisioning and operational execution, creating a more seamless workflow across Terraform and Ansible.
»Bringing actions to Terraform Stacks
We're also continuing to expand where actions can be used. Actions can now be lifecycle-triggered from Terraform Stacks configurations, extending operational automation beyond individual workspaces and into stack-based deployments.
Terraform Stacks introduce a new configuration layer, written as code, that sits on top of Terraform modules. By allowing teams to define and manage collections of related infrastructure together, Stacks provide a higher-level abstraction for coordinating infrastructure deployments across environments and teams.
With actions now supported in Stacks, teams can automatically invoke approved operational workflows in response to stack lifecycle events. This enables organizations to connect infrastructure changes with the operational tasks that often follow them, such as validation, remediation, scaling, or configuration management activities.
By extending actions to Terraform Stacks, teams can apply operational automation more consistently across complex environments, reducing manual intervention and helping operational processes scale alongside infrastructure.
»Looking ahead
Infrastructure lifecycle management requires more than provisioning resources. Organizations need consistent visibility, reliable automation, and operational workflows that work together across Day 0 provisioning, Day 1 configuration, and Day 2 operations.
To get started please refer to the links below:
If you are new to Terraform, you can get started with HashiCorp-managed HCP Terraform for free to begin provisioning and managing your infrastructure in any environment. And don’t forget to link your HCP Terraform and HashiCorp Cloud Platform (HCP) accounts for a seamless sign-in experience.
