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
On July 30 AWS Quietly Trims a Dozen Services and Walking Back Its Own AI Bets Is the Real Story
On June 30, 2026, AWS closed roughly a dozen services to new customers effective July 30, and the list is mostly its own first-generation AI and search products: Kendra, Q Business, and Bedrock Agents, now renamed Classic. But retire means three different things in this announcement, maintenance mode where existing customers keep running fully supported, sunset with a real end-of-support date, and already ended. This sorts every service into its bucket, explains why the AI cull is a consolidation onto Bedrock rather than a retreat, and covers the two migrations that need actual work: WorkSpaces PCoIP to DCV by October 2027, and Kendra to Bedrock Knowledge Bases.
CloudThe Node.js 20 Lambda Deadline Everyone Is Citing Is Wrong and the Real Risk Already Started
The AWS Lambda Node.js 20 deadline everyone is citing, August 31 and September 30, 2026, is out of date. AWS moved the block-create date to February 1, 2027 and block-update to March 3, 2027. But the number that matters is April 30, 2026, when the Node.js 20 runtime stopped getting language security patches. This covers what each date really means, the OS-versus-runtime patching nuance most guides miss, a one-command way to find every affected function, and the safe migration to nodejs22.x or nodejs24.x.
CloudAzure 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.