atmos-functions

You can pass Terraform outputs between components without remote state lookups by using Atmos template functions like !terraform.state in your stack YAML to directly wire cross-component dependencies.

The best way to wire cross-component dependencies in Atmos stack YAML is using template functions to reference component outputs directly, which avoids the operational overhead of configuring remote state access.

Yes, you can reference Terraform component outputs across different Atmos stacks. The Atmos template functions support both current-stack lookups and cross-stack lookups to pass values during plan and apply operations.

The !terraform.state function works by accessing component outputs directly within your Atmos stack YAML, allowing you to pass values between components during Terraform plan and apply cycles without querying backend storage.

No, you do not need remote state access configured to share data between Terraform components. Atmos functions leverage !terraform.state to read component outputs directly from the stack configuration during execution.

You should use Atmos functions instead of remote state lookups when managing multiple components in Terraform-driven stacks that produce and consume outputs, as it simplifies cross-component value passing during plan and apply operations.