Skip to main content

See Atmos in Action

· 3 min read
Erik Osterman
Founder @ Cloud Posse

Start with the recording.

atmos terraform plan
 
00:00.0 / 00:00.0

That is the point of this update: the docs now have short terminal casts for the parts of Atmos that are easier to understand by watching them run.

No big setup. No long pitch before the useful part. Open a page, press play, and see what happens.

New Recordings

The first set covers the runs people usually want to inspect first:

  • plan
  • deploy
  • output
  • source pull
  • stack list
  • component details
  • stack details
  • local AWS demo

Each cast is meant to answer the same question: what will I see when I run this?

Plan, Deploy, Output

The plan cast starts the set. The next two show the follow-up runs:

atmos terraform deploy
 
00:00.0 / 00:00.0
atmos terraform output
 
00:00.0 / 00:00.0

Together, they show the basic path from preview to apply to result.

Source Pull

This cast shows the source pull by itself:

atmos vendor pull
 
00:00.0 / 00:00.0

It is intentionally plain. You can see what is fetched and what the terminal prints when it finishes.

Look Around First

Sometimes the next step is to inspect the project before changing anything.

atmos list stacks
 
00:00.0 / 00:00.0
atmos describe component
 
00:00.0 / 00:00.0
atmos describe stacks
 
00:00.0 / 00:00.0

These casts show what Atmos sees before you ask it to do anything else.

Local AWS Demo

The longest cast shows a full local AWS run:

atmos emulator aws lifecycle
 
00:00.0 / 00:00.0

It brings the local service up, waits for it, runs against it, prints the result, and shuts it down.

Kept Current

The recordings are made by Atmos:

github.com/cloudposse/atmos/blob/main/demo/casts/atmos.yaml

That file builds the binary, prepares the demo files, records the casts, copies them into the website, and checks the result.

The docs get a visible example. The repo gets a repeatable way to refresh it.