RepoJournal
HashiCorp @hashicorp
176 wires and counting

$ follow HashiCorp

Keep up with HashiCorp in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-30
stories 31
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

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

By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology

modular-magician WodansSon josh-barker toby-goodlock
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

References

  1. [1] azurerm_security_center_subscription_pricing - lock using subscription id so parallel changes do not fail ↗ hashicorp/terraform-provider-azurerm
  2. [2] [azurerm_cdn_frontdoor:] Added `2025-12-01` CDN API for Front Door Rules ↗ hashicorp/terraform-provider-azurerm
  3. [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. [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. [5] compute: add list resources for disk, image, snapshot ↗ hashicorp/terraform-provider-google-beta
  6. [6] Add google_apigee_datastore resource ↗ hashicorp/terraform-provider-google-beta
  7. [7] [SecurityScanner] Add ignore_http_status_errors to google_security_scanner_scan_config ↗ hashicorp/terraform-provider-google-beta
  8. [8] Add migration center import job resource and tests ↗ hashicorp/terraform-provider-google-beta

$ ls hashicorp/reviews/ # the step-back reads

the week in review Consul provider patches two Go CVEs, adds 2.23.0 upgrade gate the month in review Consul patches four CVEs as Go bumps sweep repos
Full archive → Weekly reviews →

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.
♥

$ log @hashicorp --recent

A copyright sweep is the whole day 2 shipped HashiCorp: no material update 2 shipped Application Design Center lands, workload identity pools grow two fields 46 shipped Consul CI breaks on jq 1.8 as Ubuntu 26.04 runners arrive 31 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.