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

NOMAD PODMAN DRIVER FIXES SILENT NETWORK FAILURE

By RepoJournal · Filed · About HashiCorp

Static IP assignments were being silently ignored on Podman containers, forcing them onto DHCP despite explicit configuration.

The Nomad Podman driver had a critical bug where static IP configuration (static_ips, ipv4_address, ipv6_address, static_mac) was discarded at runtime [1]. The Networks field in ContainerNetworkConfig used an incorrect JSON tag ('newNetworks' instead of 'Networks'), causing Podman's API to silently drop the network settings. Containers would start successfully but receive dynamic DHCP addresses, creating a configuration drift that's difficult to debug in production. The fix corrects the JSON serialization and adds support for custom network name resolution [2]. On the Azure front, terraform-provider-azurerm is expanding PowerShell Core version support in function app resources [3], while acceptance tests across multiple Azure services are being hardened [4]. AWS CloudControl provider continues its steady release cadence with v1.87.0 staging [5].

Action items

References

  1. [1] fixed static IP assignment ↗ hashicorp/nomad-driver-podman
  2. [2] fixed static IP assignment (#507) hashicorp/nomad-driver-podman
  3. [3] `azurerm_windows_function_app`, `azurerm_windows_function_app_slot` - add support for `7.6` in powershell_core_version property ↗ hashicorp/terraform-provider-azurerm
  4. [4] test: `analysisservices`, `appinsights`, `arckubernetes`, `authorization`, `automation` - various acceptance test fixes ↗ hashicorp/terraform-provider-azurerm
  5. [5] Add CHANGELOG entry for v1.87.0 ↗ hashicorp/terraform-provider-awscc

FAQ

What changed in HashiCorp on May 29, 2026?
Static IP assignments were being silently ignored on Podman containers, forcing them onto DHCP despite explicit configuration.
What should HashiCorp teams do about it?
Upgrade nomad-driver-podman to latest and verify static IP assignments are honored • Audit existing Nomad containers on Podman for unintended DHCP assignments • Update to latest terraform-provider-azurerm for PowerShell 7.6 function app support
Which HashiCorp repositories shipped on May 29, 2026?
hashicorp/nomad-driver-podman, hashicorp/terraform-provider-azurerm, hashicorp/terraform-provider-awscc

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.