RepoJournal
HashiCorp

@hashicorp

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

Pick a date

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

The Wire · Showcase

CONSUL ADDS ENTERPRISE EXTERNAL AUTH LAYER, DOCS SHED DEPRECATED HVAULT CODE

By RepoJournal · Filed · About HashiCorp

Consul's API Gateway now supports external authorization enforcement through a new enterprise-only surface, while the docs team systematically removes HashiVault references across the unified platform.

Consul shipped a three-layer config model for external authorization (`ext_authz`) on its API Gateway [1], with the enforcement behavior gated to enterprise customers while the shared CE surface ships in the open codebase. This keeps the feature invisible in community editions but ready for enterprise deployments without additional maintenance burden. The release is backed by fresh hygiene workflows [2] that will catch release engineering issues before they ship, though these checks run non-blocking initially to let teams adjust. On the docs front, HashiVault references are being systematically purged from the Vault Secrets Operator, API references, and supporting materials [ref:5,ref:7], with proper redirect chains already verified and HVS CLI docs moved to the deprecated directory [4]. A separate fix addresses a malformed table in the explorer API reference . Packer's plugin SDK caught up on module dependencies and fixed an unchecked error condition [5], a small but necessary hygiene win.

Action items

References

  1. [1] config-entry(api-gateway): add ext_authz filter surface (Enterprise only) ↗ hashicorp/consul
  2. [2] Adding release hygiene workflows ↗ hashicorp/consul
  3. [3] Claude VSO cleanup ↗ hashicorp/web-unified-docs
  4. [4] Move HVS CLI docs and remove references to use cases ↗ hashicorp/web-unified-docs
  5. [5] Updated Go Modules ↗ hashicorp/packer-plugin-sdk

FAQ

What changed in HashiCorp on July 3, 2026?
Consul's API Gateway now supports external authorization enforcement through a new enterprise-only surface, while the docs team systematically removes HashiVault references across the unified platform.
What should HashiCorp teams do about it?
Review Consul API Gateway ext_authz config for enterprise readiness if using external authorization • Update any internal links pointing to HVS documentation to use redirects or deprecated paths • Upgrade packer-plugin-sdk to latest if you maintain downstream plugins
Which HashiCorp repositories shipped on July 3, 2026?
hashicorp/consul, hashicorp/web-unified-docs, hashicorp/packer-plugin-sdk

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.