Who contributed to HashiCorp on May 30, 2026?

4 developers shipped this update, including josh-barker, WodansSon, toby-goodlock, and modular-magician.

What were the notable HashiCorp updates?

azurerm_security_center_subscription_pricing - lock using subscription id so parallel changes do not fail, [azurerm_cdn_frontdoor:] Added `2025-12-01` CDN API for Front Door Rules, and `azurerm_data_protection_backup_instance_data_lake_storage` - add FriendlyName on Create to align with other backup instance resources.

@hashicorp

Terraform, Vault, Consul - infra-as-code for ops teams

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

AZURE TERRAFORM PROVIDER LOCKS DOWN SECURITY CENTER, GOOGLE BETA ADDS THREE NEW LIST RESOURCES

By RepoJournal · Filed 06:01 UTC on May 30, 2026 · About HashiCorp

4 people shipped this

modular-magician @modular-magician 4 cited

WodansSon @WodansSon 2 cited

josh-barker @josh-barker 1 cited

toby-goodlock @toby-goodlock 1 cited

HashiCorp's Azure provider is tightening concurrency controls while Google Cloud gains bulk data query capabilities across compute resources.

The terraform-provider-azurerm team shipped a critical reliability fix [1] that locks security center pricing operations by subscription ID, preventing race conditions when parallel Terraform runs modify the same subscription. This solves a real operational pain point for teams managing multiple Azure subscriptions simultaneously. On the feature front, Azure's CDN Front Door now supports the latest 2025-12-01 API [2], while data protection backup instances gained FriendlyName support [3] to match the broader backup resource pattern, and orchestrated virtual machine scale sets now expose the Prioritized allocation strategy [4] with rank field visibility. Over in Google Cloud, the terraform-provider-google-beta landed three new list resources [5] for compute.disk, compute.image, and compute.snapshot, letting teams query resources in bulk instead of individual lookups. The same provider added a new google_apigee_datastore resource [6] for managing analytics export destinations, Security Scanner now ignores HTTP status errors on demand [7], and migration center gained import job resource support [8].

Action items

→ If managing Azure subscriptions with parallel Terraform, upgrade terraform-provider-azurerm immediately to avoid race conditions hashicorp/terraform-provider-azurerm [immediate]
→ Plan upgrade to google-beta to leverage new list resource capabilities for compute queries hashicorp/terraform-provider-google-beta [plan]
→ Monitor nightly builds of nomad-autoscaler, nomad-driver-podman, and nomad-pack for upcoming release features hashicorp/nomad-autoscaler [monitor]

References

[1] azurerm_security_center_subscription_pricing - lock using subscription id so parallel changes do not fail ↗ hashicorp/terraform-provider-azurerm
[2] [azurerm_cdn_frontdoor:] Added `2025-12-01` CDN API for Front Door Rules ↗ hashicorp/terraform-provider-azurerm
[3] `azurerm_data_protection_backup_instance_data_lake_storage` - add FriendlyName on Create to align with other backup instance resources ↗ hashicorp/terraform-provider-azurerm
[4] [ENHANCEMENT]: `azurerm_orchestrated_virtual_machine_scale_set` - add support for the `Prioritized` `allocation_strategy`, expose `rank` field in the `sku_profile` `vm_sizes` code block ↗ hashicorp/terraform-provider-azurerm
[5] compute: add list resources for disk, image, snapshot ↗ hashicorp/terraform-provider-google-beta
[6] Add google_apigee_datastore resource ↗ hashicorp/terraform-provider-google-beta
[7] [SecurityScanner] Add ignore_http_status_errors to google_security_scanner_scan_config ↗ hashicorp/terraform-provider-google-beta
[8] Add migration center import job resource and tests ↗ hashicorp/terraform-provider-google-beta

Quick answers

What shipped in HashiCorp on May 30, 2026?: HashiCorp's Azure provider is tightening concurrency controls while Google Cloud gains bulk data query capabilities across compute resources. In total, 14 commits, 14 pull requests, and 3 releases landed.
Who contributed to HashiCorp on May 30, 2026?: 4 developers shipped this update, including josh-barker, WodansSon, toby-goodlock, and modular-magician.
What were the notable HashiCorp updates?: azurerm_security_center_subscription_pricing - lock using subscription id so parallel changes do not fail, [azurerm_cdn_frontdoor:] Added `2025-12-01` CDN API for Front Door Rules, and `azurerm_data_protection_backup_instance_data_lake_storage` - add FriendlyName on Create to align with other backup instance resources.

TERRAFORM PROVIDERS EXPAND GOOGLE CLOUD COVERAGE AND IN-PLACE UPDATES

HashiCorp shipped in-place VCS connection updates for registry modules while Google provider gains traffic config for Vertex AI and promotes NCC gateway resources to GA.

go 19 shipped 1-min read

@hashicorp 1 day ago

VAULT LDAP GETS ON-DEMAND PASSWORD ROTATION, PACKER CUTS v1.16.0

Terraform provider for Vault now supports rotate-on-read for LDAP secrets, letting teams rotate credentials at read time instead of waiting for scheduled intervals.

go 8 shipped 1-min read

@hashicorp 2 days ago

CONSUL FIXES FLOODED MEMBER REJOIN BUG AS VSO PATCHES GRPC FRAME FLOOD

Consul patches a critical WAN flood regression that was incorrectly treating failed members as alive during rejoin sequences.

go 8 shipped 1-min read

@hashicorp 3 days ago

TERRAFORM AWS PROVIDER GAINS S3 TABLES AND OPENSEARCH FEDERATION SUPPORT

The AWS provider shipped three enhancement PRs overnight that expand infrastructure-as-code coverage for S3 Tables metadata properties and OpenSearch security configurations, while the docs team cleaned up deprecated tutorial collections and fixed formatting bugs across Vault and PKI documentation.

go 60 shipped 1-min read

Elsewhere on the wire

AI Agents about 10 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 10 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.