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.
One email a day. Unsubscribe in one click.
Keep up with HashiCorp in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review the Python-TFE relationships docs and update your integration patterns to use ?include= for batch resource loading hashicorp/python-tfe [plan]
- → Test nightly Nomad Podman and Autoscaler builds in non-production if you're tracking pre-release features hashicorp/nomad-driver-podman [monitor]
References
- [1] feat(relationships): fill related data from ?include= and make all related resources accessible ↗ hashicorp/python-tfe
- [2] nightly ↗ hashicorp/nomad-driver-podman
- [3] nightly ↗ hashicorp/nomad-autoscaler