The Wire · Showcase
AZURE TERRAFORM PROVIDER LOCKS DOWN SECURITY CENTER, GOOGLE BETA ADDS THREE NEW LIST RESOURCES
By RepoJournal · Filed · About HashiCorp
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
FAQ
- What changed 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.
- What should HashiCorp teams do about it?
- If managing Azure subscriptions with parallel Terraform, upgrade terraform-provider-azurerm immediately to avoid race conditions • Plan upgrade to google-beta to leverage new list resource capabilities for compute queries • Monitor nightly builds of nomad-autoscaler, nomad-driver-podman, and nomad-pack for upcoming release features
- Which HashiCorp repositories shipped on May 30, 2026?
- hashicorp/terraform-provider-azurerm, hashicorp/terraform-provider-google-beta