Who contributed to HashiCorp on August 7, 2026?

6 developers shipped this update, including gbaker-ibm, shani34, dependabot, shashankNandigama, santoshpulluri, and kt.

What were the notable HashiCorp updates?

fix(apigw): resolve composed service-router destinations as http during gateway synthesis, fix(apigw): resolve composed service-router destinations as http during gateway synthesis (#23793), and Bump google.golang.org/grpc from 1.72.2 to 1.82.1 in /integration-tests.

@hashicorp

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

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

CONSUL API GATEWAY FIX STOPS 503 CASCADES IN MULTI-PARTITION SETUPS

By RepoJournal · Filed 06:57 UTC on August 7, 2026 · About HashiCorp

6 people shipped this

kt @katbyte 5 cited

shani34 @shani34 2 cited

santoshpulluri @santoshpulluri 2 cited

dependabot @dependabot 1 cited

gbaker-ibm @gbaker-ibm

shashankNandigama @shashankNandigama

Consul Enterprise users hitting HTTP 503s after upgrading to 2.0.x now have a fix: API gateways with HTTP listeners were resolving downstream services with wrong protocols, breaking discovery chains in peered clusters.

The root cause is in gateway synthesis. When API gateways compose service-router destinations, they were resolving backends as TCP by default instead of respecting HTTP protocol overrides, triggering cluster_not_found errors in multi-partition and cluster-peering topologies [1] [2]. This fix resolves composed service-router destinations as HTTP during gateway synthesis, eliminating the protocol mismatch that cascaded into widespread 503s. Meanwhile, Consul dataplane is quieting noisy logs from UDP timeout chatter [4] [5], and gRPC bumped to 1.82.1 with security hardening against frame flood attacks [3]. On the Azure provider side, the team is cleaning house by removing all 5.0 feature flag gates across legacy, monitor, containers, arc-kubernetes, authorization, automation, batch, and ioThub modules [6] [7] [8] [9] [10], signaling that 5.0 is now the stable baseline and legacy code paths can be junked.

Action items

→ Deploy Consul fix for API gateway 503s immediately if running 2.0.x with peering or multi-partition setups hashicorp/consul [immediate]
→ Upgrade gRPC to 1.82.1 in consul-dataplane to patch frame flood vulnerability hashicorp/consul-dataplane [plan]
→ Plan removal of 5.0 feature flag gates from your Azure provider code hashicorp/terraform-provider-azurerm [monitor]

References

[1] fix(apigw): resolve composed service-router destinations as http during gateway synthesis ↗ hashicorp/consul
[2] fix(apigw): resolve composed service-router destinations as http during gateway synthesis (#23793) hashicorp/consul
[3] Bump google.golang.org/grpc from 1.72.2 to 1.82.1 in /integration-tests ↗ hashicorp/consul-dataplane
[4] Removal of noisy log ↗ hashicorp/consul-dataplane
[5] Removal of noisy log (#1198) hashicorp/consul-dataplane
[6] remove 5.0 feature flag gates from legacy (#32993) hashicorp/terraform-provider-azurerm
[7] remove 5.0 feature flag gates from monitor (#32990) hashicorp/terraform-provider-azurerm
[8] remove 5.0 feature flag gates from arckubernetes, authorization, automation and batch (#32994) hashicorp/terraform-provider-azurerm
[9] remove 5.0 feature flag gates from containers (#32991) hashicorp/terraform-provider-azurerm
[10] remove 5.0 feature flag gates from iothub (#32995) hashicorp/terraform-provider-azurerm

Quick answers

What shipped in HashiCorp on August 7, 2026?: Consul Enterprise users hitting HTTP 503s after upgrading to 2.0.x now have a fix: API gateways with HTTP listeners were resolving downstream services with wrong protocols, breaking discovery chains in peered clusters. In total, 21 commits and 24 pull requests landed.
Who contributed to HashiCorp on August 7, 2026?: 6 developers shipped this update, including gbaker-ibm, shani34, dependabot, shashankNandigama, santoshpulluri, and kt.
What were the notable HashiCorp updates?: fix(apigw): resolve composed service-router destinations as http during gateway synthesis, fix(apigw): resolve composed service-router destinations as http during gateway synthesis (#23793), and Bump google.golang.org/grpc from 1.72.2 to 1.82.1 in /integration-tests.

AZURE PROVIDER TIGHTENS TEST DISCIPLINE, LINT RULES EXPAND 39 TO 70

Terraform's Azure provider is shipping stricter acceptance test guards and a major linting overhaul that caught two real bugs in the codebase.

go 41 shipped

@hashicorp Aug 6

TERRAFORM PROVIDER CLEANUP PUSHES FORWARD; CONSUL HARDENS RELEASE PIPELINE

HashiCorp is systematically removing feature flags across the Azure provider while Consul teams move security scanning upstream in their release workflows.

go 36 shipped

@hashicorp Aug 5

TERRAFORM AWS PROVIDER SHIPS MAJOR VERSIONS WITH ELASTICACHE AND ECS EXPANSIONS

Terraform AWS provider v6.34.0 through v6.57.1 landed overnight with ElastiCache fixes, new ECS capacity reservation support, and the second MailManager resource joining the roster.

go 68 shipped

@hashicorp Aug 4

TERRAFORM GRAPH INTERNALS STRIPPED FOR SPEED

James Bardin just yanked five layers of unused abstractions out of Terraform's core graph engine, clearing the path for what comes next.

go 25 shipped

Elsewhere on the wire

AI Agents Aug 8

LANGCHAIN PATCHES CLAUDE FILE TOOLS AND OPENAI CONTEXT ERRORS

LangChain shipped langchain-openai 1.4.2 with fixes for context window overflows and broken Claude rename operations, while OpenHands v1.11.0 adds per-run LLM cost tracking.

ai-agents 99 shipped

Local LLMs Aug 8

OLLAMA SHIPS BLOCK-DIFFUSION SPECULATIVE DECODING, SGLANG LAUNCHES KIMI K3 DAY-0

Draft models just got faster: Ollama merged DFlash block-diffusion speculative decoding that proposes entire token sequences in one forward pass, while SGLang shipped production-ready support for Kimi K3, a 2.8T-parameter multimodal LatentMoE that routes through a latent space with 896 experts.

+12

llms 263 shipped

@CachyOS Aug 8

CACHYOS AUTOMATION PUSHES BROWSER UPDATES ACROSS THE STACK

Five browser and utility packages shipped overnight with automated version bumps, while the Welcome interface gains Traditional Chinese support and translation cleanup hits the queue.

infra 51 shipped

Elixir & Phoenix Aug 8

ELIXIR PARSER GETS LEANER AS PHOENIX AUDITS DEAD CODE

Daniel Kukula shipped three consecutive optimizations to Elixir's date parsing pipeline, removing accumulators and intermediate allocations in a focused performance push [ref:1] [ref:2] [ref:3].