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

GO-TFE SHIPS PROVIDER SET CRUD AND REGISTRY READS IN V1.107.0

By RepoJournal · Filed · About HashiCorp

HashiCorp's Terraform Enterprise Go client unlocked atomic provider set management and registry provider lookup by ID, completing the API surface teams need for no-code infrastructure.

go-tfe v1.107.0 [1] lands three critical API additions that unblock Terraform Enterprise workflows. The centerpiece is full CRUD support for ProviderSets [2] with atomic update semantics, meaning a single PATCH request can now change global, project, and workspace assignments without race conditions. Callers can also read registry providers by unique identifier [1] and access the SourceModuleID field [3] on workspaces provisioned from no-code modules, exposing infrastructure patterns the API already tracked but the client couldn't surface. On the Nomad side, a UI region-switch bug [4] that silenced allocation data is fixed, and the agent reload endpoint [5] now ships with ACL support, letting operators reload config remotely without SSH access. consul-ecs [6] reverted its v2 API experiment and locked back to the stable v1.34.3 API surface, ending a compatibility mismatch. These are all shipping to production readiness, not experimental features.

Action items

References

  1. [1] v1.107.0 ↗ hashicorp/go-tfe
  2. [2] `provider_set` resource ↗ hashicorp/go-tfe
  3. [3] feat(workspace): expose source-module-id attribute (#1331) hashicorp/go-tfe
  4. [4] ui: NMD 917 - UI not updating on region switch (#27886) hashicorp/nomad
  5. [5] Allow Agent Reload with API - /v1/agent/reload ↗ hashicorp/nomad
  6. [6] fix: update imports to remove v2 consul api (#343) hashicorp/consul-ecs

FAQ

What changed in HashiCorp on May 27, 2026?
HashiCorp's Terraform Enterprise Go client unlocked atomic provider set management and registry provider lookup by ID, completing the API surface teams need for no-code infrastructure.
What should HashiCorp teams do about it?
Upgrade go-tfe to v1.107.0 if you manage provider sets or no-code modules • Test Nomad UI region switching after updating to latest; allocations should now refresh correctly • Update consul-ecs deployments to use v1 API imports; revert from v2 API if applied
Which HashiCorp repositories shipped on May 27, 2026?
hashicorp/go-tfe, hashicorp/nomad, hashicorp/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.