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

PYTHON-TFE NOW HYDRATES RELATED RESOURCES FROM API INCLUDES

By RepoJournal · Filed · About HashiCorp

The Python Terraform Enterprise SDK can now automatically populate related resources when you request them with ?include= parameters, eliminating manual data assembly in your TFE integrations.

Python-TFE shipped a major relationships feature [1] that transforms how you work with nested TFE data. Instead of fetching a workspace and then making separate calls to load its runs, variables, and state versions, the SDK now hydrates all related resources directly from the API's include parameter, cutting network calls and simplifying integration code. This lands as a significant quality-of-life improvement for anyone building tooling on top of TFE, especially teams managing multi-workspace infrastructure. On the plugin side, both the Nomad Podman driver [2] and Nomad Autoscaler [3] posted nightly builds with development snapshots available for early testing. These are for operators who want to validate their configurations against bleeding-edge code before stable releases ship.

Action items

References

  1. [1] feat(relationships): fill related data from ?include= and make all related resources accessible ↗ hashicorp/python-tfe
  2. [2] nightly ↗ hashicorp/nomad-driver-podman
  3. [3] nightly ↗ hashicorp/nomad-autoscaler

FAQ

What changed in HashiCorp on June 19, 2026?
The Python Terraform Enterprise SDK can now automatically populate related resources when you request them with ?include= parameters, eliminating manual data assembly in your TFE integrations.
What should HashiCorp teams do about it?
Review the Python-TFE relationships docs and update your integration patterns to use ?include= for batch resource loading • Test nightly Nomad Podman and Autoscaler builds in non-production if you're tracking pre-release features
Which HashiCorp repositories shipped on June 19, 2026?
hashicorp/python-tfe, hashicorp/nomad-driver-podman, hashicorp/nomad-autoscaler

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.