Terraform providers widen AWS, Azure, and Google coverage while core clears Graph cruft

The month's biggest weight fell on the major Terraform providers. The AWS provider shipped major versions with ElastiCache and ECS expansions [1], while the Azure provider cleared its 5.0 deprecation gates, stripped feature flags, and burned 373 linter violations [2]. On the Google side, both google and google-beta providers gained Cloud Run v2 scaling controls, allow_global_access for network services gateways, backupdr resource fixes, and Attached Disk config in dataproc [3][4][5][6]. This breadth signals a push to reduce configuration friction across all three clouds.

Terraform core made a deliberate move to simplify its graph internals. It removed the unused Grapher/SubGrapher interfaces, stripped unused set values, and dropped VertexName [7][8][9]. These are internal cleanups, not user-facing changes, but they set the stage for faster graph operations. Meanwhile, Terraform 1.16 RC landed with provider state persistence, hinting at upcoming stability and performance gains in the 1.16 release [10].

Beyond Terraform, Consul and Nomad each made meaningful platform improvements. Consul bumped its Go version to 1.26.5 [1] and shipped dynamic feature gates, while a fix to the API Gateway prevented 503 cascades in multi-partition setups [11]. Nomad dropped the deprecated pointerOf helper, moved from multierror to stdlib, and cut pointer boilerplate across the codebase [8]. These changes reduce maintenance burden and improve reliability for operators.

The HashiCorp ecosystem also embraced nightly builds and security hygiene. Nightly snapshots went live for multiple projects, including nomad-driver-podman and nomad-pack [13], and Consul fixed js-yaml and nanoid vulnerabilities [12]. These routine but essential efforts keep the projects healthy and responsive.

The through-line: HashiCorp is investing in provider depth, reducing technical debt in core, and tightening release pipelines across the board. For users, that translates to fewer breaking changes, faster graph execution, and more configuration options at the edge.