RepoJournal
HashiCorp

@hashicorp

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

Pick a date

  1. Sun 3 may
  2. Tue 5 may
  3. Wed 6 may
  4. Thu 7 may
  5. Fri 8 may
  6. Sat 9 may
  7. Sun 10 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

TERRAFORM AZURE PROVIDER GAINS BROAD SERVICE COVERAGE ACROSS 5 PULL REQUESTS

By RepoJournal · Filed · About HashiCorp

HashiCorp shipped five separate PRs expanding terraform-provider-azurerm support across services S through W, while Packer's Amazon plugin fixes critical retry failures.

The terraform-provider-azurerm team moved five feature additions into review overnight, each adding support for two new Azure services [1] [2] [3] [4] [5]. These span Services E through W, representing methodical expansion of the provider's surface area across multiple Azure offerings. Over on the Packer side, amazon-plugin v1.8.1 [6] shipped a critical fix for ShouldRetry callbacks that were silently dropping errors, causing transient AWS API failures like InvalidAMIID.NotFound and InvalidSnapshot.NotFound to bypass retry logic entirely [6]. The plugin also tightened IAM instance profile propagation to eliminate race conditions during launch [6]. Routine dependency bumps landed across vscode-terraform (qs package update) and homebrew-tap (workflow-dispatch action) , both low-priority maintenance moves.

Action items

References

  1. [1] Services `S`/`T`/`V`/`W` - add support for 2 new features ↗ hashicorp/terraform-provider-azurerm
  2. [2] Services `P`/`Q`/`R` - add support for 2 new features ↗ hashicorp/terraform-provider-azurerm
  3. [3] Services `N`/`O` - add support for 2 new features ↗ hashicorp/terraform-provider-azurerm
  4. [4] Services `K`/`L`/`M` - add support for 2 new features ↗ hashicorp/terraform-provider-azurerm
  5. [5] Services `E`/`F`/`G`/`H`/`I` - add support for 2 new features ↗ hashicorp/terraform-provider-azurerm
  6. [6] v1.8.1 ↗ hashicorp/packer-plugin-amazon

FAQ

What changed in HashiCorp on May 26, 2026?
HashiCorp shipped five separate PRs expanding terraform-provider-azurerm support across services S through W, while Packer's Amazon plugin fixes critical retry failures.
What should HashiCorp teams do about it?
Review and vote on terraform-provider-azurerm PRs to prioritize Azure service coverage expansion • Upgrade Packer amazon-plugin to v1.8.1 if using transient-sensitive AWS operations
Which HashiCorp repositories shipped on May 26, 2026?
hashicorp/terraform-provider-azurerm, hashicorp/packer-plugin-amazon

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.