RepoJournal
HashiCorp

@hashicorp

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

Pick a date

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

The Wire · Showcase

CONSUL-ECS FIXES HEALTH-CHECK RACE CONDITION ACROSS AWS

By RepoJournal · Filed · About HashiCorp

Consul's ECS integration just eliminated a critical race condition that could leave service and proxy health checks diverged in production.

The consul-ecs team shipped an atomic batching fix [1] that consolidates three separate Catalog.Register calls into a single operation during health sync cycles. Previously, partial failures could desynchronize service-side and proxy-side dataplane checks, creating a silent failure mode where traffic routing decisions were based on stale health state. This is the kind of bug that doesn't surface in staging. Alongside this fix, both terraform-aws-consul-ecs [2] and consul-ecs [3] are bumping serf to 0.10.4 and consul-api to 1.34.4, addressing upstream dependency drift. The health-sync batching change is the story here; the dependency updates are table stakes. There's also a stageContainerHealthChecks refactor [4] landing in parallel to clean up the surrounding code path.

Action items

References

  1. [1] health-sync: batch Consul health check updates into a single atomic Catalog.Register ↗ hashicorp/consul-ecs
  2. [2] chore(deps): update serf and consul-api versions ↗ hashicorp/terraform-aws-consul-ecs
  3. [3] chore(deps): update serf and consul-api versions ↗ hashicorp/consul-ecs
  4. [4] refactor stageContainerHealthChecks hashicorp/consul-ecs

FAQ

What changed in HashiCorp on July 8, 2026?
Consul's ECS integration just eliminated a critical race condition that could leave service and proxy health checks diverged in production.
What should HashiCorp teams do about it?
Review the atomic health-sync fix [ref:4] and plan deployment before next consul-ecs release • Merge dependency updates [ref:1] and [ref:3] to stay current on serf and consul-api
Which HashiCorp repositories shipped on July 8, 2026?
hashicorp/consul-ecs, hashicorp/terraform-aws-consul-ecs

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.