Skip to main content

atmos list values

The atmos list values command displays component values across all stacks where the component is used.

Usage​

atmos list values [component] [flags]

Description​

The atmos list values command helps you inspect component values across different stacks. It provides a tabular view where:

  • Each column represents a stack (e.g., dev-ue1, staging-ue1, prod-ue1)
  • Each row represents a key in the component's configuration
  • Cells contain the values for each key in each stack

The command is particularly useful for:

  • Comparing component configurations across different environments
  • Verifying values are set correctly in each stack
  • Understanding how a component is configured across your infrastructure

Flags​

--query string
Dot-notation path query to filter values (e.g., .vars.enabled). Uses a simplified path syntax, not full JMESPath.
--abstract
Include abstract components in the output
--max-columns int
Maximum number of columns to display (default: 10)
--format string
Output format: table, json, csv, tsv (default: table)
--delimiter string
Delimiter for csv/tsv output (default: , for csv, \t for tsv)

Examples​

List all values for a component:

atmos list values vpc

List only variables for a component (using the alias):

atmos list vars vpc

List values with a custom path query:

# Query specific variables
atmos list values vpc --query .vars.enabled

# Query environment settings
atmos list values vpc --query .vars.environment

# Query network configuration
atmos list values vpc --query .vars.ipv4_primary_cidr_block

Include abstract components:

atmos list values vpc --abstract

Limit the number of columns:

atmos list values vpc --max-columns 5

Output in different formats:

# JSON format for machine processing
atmos list values vpc --format json

# CSV format for spreadsheet compatibility
atmos list values vpc --format csv

# TSV format with tab delimiters
atmos list values vpc --format tsv

# Note: Use JSON or CSV formats when dealing with wide datasets
# The table format will show a width error if the data is too wide for your terminal

Example Output​

> atmos list vars vpc
┌──────────────┬──────────────┬──────────────┬──────────────┐
│              │   dev-ue1    │  staging-ue1 │   prod-ue1   │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ enabled      │ true         │ true         │ true         │
│ name         │ dev-vpc      │ staging-vpc  │ prod-vpc     │
│ cidr_block   │ 10.0.0.0/16  │ 10.1.0.0/16  │ 10.2.0.0/16  │
│ environment  │ dev          │ staging      │ prod         │
│ namespace    │ example      │ example      │ example      │
│ stage        │ dev          │ staging      │ prod         │
│ region       │ us-east-1    │ us-east-1    │ us-east-1    │
└──────────────┴──────────────┴──────────────┴──────────────┘

Nested Object Display​

When listing values that contain nested objects:

  1. In table format, nested objects appear as {...} placeholders
  2. Use --format json or --format yaml to see the complete nested structure
  3. You can query specific nested paths using the dot notation: --query .vars.tags.Environment

Example JSON output with nested objects:

{
  "dev-ue1": {
    "cidr_block": "10.0.0.0/16",
    "tags": {
      "Environment": "dev",
      "Team": "devops"
    },
    "subnets": [
      "10.0.1.0/24",
      "10.0.2.0/24"
    ]
  }
}