atmos-functions

Automate cross-component output passing in Terraform stacks with Atmos template functions.

98|34|Updated Apr 27, 2018

Search Tags:#automation #terraform #lookups #atmos-functions #stack-yaml #component-outputs #cross-component

Ready to run

npx skills add https://github.com/cloudposse/docs --skill atmos-functions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atmos-functions
Source: https://github.com/cloudposse/docs/tree/main/examples/snippets/.claude/skills/atmos-functions
Command: npx skills add https://github.com/cloudposse/docs --skill atmos-functions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wiring cross-component dependencies in Terraform-driven stacks using Atmos template functions to pass outputs between components without remote-state lookups.

Core Features & Use Cases

Cross-component dependency wiring with Atmos functions in stack YAML
Efficient access to component outputs without remote Terraform state lookups
Supports both current-stack lookups and cross-stack lookups

Quick Start

Wiring a component output with !terraform.state in your stack YAML to pass data between components.

Frequently Asked Questions about atmos-functions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I pass Terraform outputs between components without remote state lookups?▼

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.

What is the best way to wire cross-component dependencies in Atmos stack YAML?▼

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.

Can I reference Terraform component outputs across different Atmos stacks?▼

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.

How does !terraform.state work for passing values in Terraform stacks?▼

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.

Do I need remote state access configured to share data between Terraform components?▼

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.

When should I use Atmos functions instead of direct remote state lookups in Terraform?▼

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.