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

HASHICORP DROPS BETA TAGS, TIGHTENS SECURITY REQUIREMENTS ACROSS TERRAFORM AND CONSUL

By RepoJournal · Filed · About HashiCorp

Project-level run tasks ship out of beta while Admin Center now requires HTTPS, signaling tightened security posture across the HashiCorp stack.

The documentation desk shipped three major clarity updates overnight. Project-level run tasks graduated from beta [1], HVS docs are being deprecated and removed from navigation [2] [3] [4], and Admin Center now mandates HTTPS for all deployments [5]. On the Kubernetes provider front, v3.2.1 landed to fix identity change errors and resource creation issues that plagued longer provisioning workflows [6]. The Nomad Podman driver is expanding what it can pull: HTTP(S) URLs now work for oci-archive and docker-archive images, letting jobs fetch one-off builds from web servers and object stores instead of local filesystem only [7]. Meanwhile, Consul-K8s is migrating internal metrics instrumentation from the archived armon/go-metrics to HashiCorp's own fork [8], and Consul itself upgraded Nomad and Vault compatibility testing to validate against latest versions [9].

Action items

References

  1. [1] Remove beta tag from project-level run tasks (#2726) hashicorp/web-unified-docs
  2. [2] Remove HVS from devDot nav hashicorp/web-unified-docs
  3. [3] Remove HVS from devDot nav (#2758) hashicorp/web-unified-docs
  4. [4] Move HVS docs to deprecated directory hashicorp/web-unified-docs
  5. [5] docs: Admin Center requires HTTPS (#2757) hashicorp/web-unified-docs
  6. [6] v3.2.1 ↗ hashicorp/terraform-provider-kubernetes
  7. [7] support http(s) URLs for oci-archive/docker-archive images ↗ hashicorp/nomad-driver-podman
  8. [8] Migrate armon/go-metrics to hashicorp/go-metrics and update Go dependencies ↗ hashicorp/consul-k8s
  9. [9] Compatibility testing for nomad and vault versions with latest version (#23624) hashicorp/consul

FAQ

What changed in HashiCorp on July 1, 2026?
Project-level run tasks ship out of beta while Admin Center now requires HTTPS, signaling tightened security posture across the HashiCorp stack.
What should HashiCorp teams do about it?
Review Admin Center HTTPS requirement documentation before next deployment • Plan HVS documentation migration to deprecated location • Update Terraform Kubernetes provider to v3.2.1 to resolve resource identity issues
Which HashiCorp repositories shipped on July 1, 2026?
hashicorp/web-unified-docs, hashicorp/terraform-provider-kubernetes, hashicorp/nomad-driver-podman, hashicorp/consul-k8s, hashicorp/consul

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.