Support output references from Ansible stacks
Support for generating output references from Ansible stacks, via an “outputs.env” file or a similar mechanism. This would allow Ansible based stacks to expose values that can be consumed by dependent stacks in the same way Terraform stacks already do.
- Workaround
- None
- Problem
Log in to comment and vote
Comments2
Magenta Spaghetti
Dec 23, 2025
In our case this comes from large, interconnected environments, where stacks are owned by different teams. Tool choice is often down to team preference or domain fit, and it’s not something we want to dictate across boundaries.
As a simplified example, Team A may use an Ansible stack to provision storage. That stack produces concrete data like volume IDs or export paths. Team B then needs those values to attach and mount the storage, and to feed into their own Terraform or Ansible stacks.
We see flows like Ansible to Ansible, or Ansible to Terraform, as responsibility moves between teams. In those cases Ansible stacks are not leaves, they sit in the middle of the dependency graph.
What we’re looking for is a simple, explicit way for stack types other than Terraform to expose outputs that dependent stacks can consume, in the same spirit as Terraform outputs.
Black Breeze
Dec 16, 2025
Hi Brendan! Thanks for raising this. Can you please describe a detailed use case of passing environment variables from one Ansible stack to another? What we’re typically seeing with Ansible stacks is that given that Ansible is primarily used for configuration management they’re pretty much always leaves of the dependency tree.
I’m not against doing this in principle but I’d love to understand the use case and the trade-offs before we start adding features to the product.