Terraform 1.8 Released with Provider Functions
HashiCorp has released Terraform 1.8, introducing provider-defined functions - the most significant language enhancement since Terraform 1.0. This release also includes improved refactoring support and state management improvements.
Provider-Defined Functions
Providers can now expose custom functions callable directly in HCL configuration. The AWS provider, for example, offers functions for ARN parsing and CIDR calculations:
locals {
account_id = provider::aws::arn_parse(var.role_arn).account_id
subnets = provider::aws::cidr_subnets("10.0.0.0/16", 8, 8, 8, 8)
}
This eliminates the need for external data sources or complex regex patterns that were previously required for common operations.
Improved Refactoring with Removed Block
The new removed block allows declaring that a resource has been removed from Terraform management without destroying it:
removed {
from = aws_instance.legacy_server
lifecycle { destroy = false }
}
State Management
Terraform 1.8 improves state file handling for large configurations, reducing plan times by up to 40 percent for configurations managing thousands of resources.
Upgrade Path
Terraform 1.8 is backward compatible with 1.x configurations. The state file format has not changed, so upgrades are safe to perform in place. Review your lock file after upgrading to ensure provider versions are compatible.
Terraform 1.8 is a recommended upgrade for all teams using Terraform, with no breaking changes and meaningful developer experience improvements.
Talk to the engineer who will own your stack.
No account managers, no offshore handoff. Senior DevOps, direct. Tell us what you are dealing with and you get a straight answer.
Related News
Azure Returns 410 Gone for GPT-4o on October 1 and Auto-Upgrade Skips the Deployments That Matter
On October 1, 2026, Azure OpenAI in Microsoft Foundry retires the GA gpt-4o (2024-11-20) and gpt-4o-mini (2024-07-18) versions, after which calls to a retired deployment return HTTP 410 Gone. Standard-family deployments are auto-upgraded region by region, but Provisioned (PTU) deployments and anything set to NoAutoUpgrade are not, and Microsoft says the date is not extendable.
CloudStay on EKS 1.33 and AWS Starts Billing You 6x From August
Amazon EKS Kubernetes 1.33 leaves standard support on July 29, 2026, and any cluster still on it is enrolled in extended support by default at six times the standard control-plane rate. The hourly charge rises from 0.10 to 0.60 US dollars per cluster, and the standard patch cadence narrows. Fleets with many clusters feel it first.
CloudAWS Shuts Down App Mesh for Good on September 30 and Your Service Mesh Goes With It
AWS ends all support for App Mesh on September 30, 2026, after which the console and every App Mesh resource go dark and the Envoy data plane is no longer managed. New onboarding has been blocked since September 24, 2024. For ECS, AWS points to Service Connect; EKS teams have their own path.