Back to changelog
New
2 minute read

atlas cloud: Manage Registry Resources from the CLI

The new atlas cloud command group lets you manage and inspect Atlas Registry resources - repositories, databases, and migration events - directly from the command line.

Until now, your repositories and their deployment status were only visible in the Atlas Cloud UI. These commands bring the same data to your terminal, so you can query deployment status from scripts, CI checks, or an AI agent, and shape the output with Go templates.

Repositories

atlas cloud repo manages Registry repositories of type schema or migration_directory. Create a new, empty repository directly from the CLI:

atlas cloud repo create
atlas cloud repo create --type migration_directory --name myapp --driver postgres
Output
Slug myapp
Title My App
Type MIGRATION_DIRECTORY
URL atlas://myapp
Driver postgres
Databases Synced 0
Databases Failed 0
Databases Pending 0

List the repositories available to you, with a summary of their databases by sync status:

atlas cloud repo list
atlas cloud repo list
Output
────── DATABASES ──────
SLUG TYPE SYNCED FAILED PENDING
payments MIGRATION_DIRECTORY 42 3 1
inventory SCHEMA 7 0 12
billing MIGRATION_DIRECTORY 0 0 0
--------------------------------
Page: 1 Page Size: 6 Total: 18

Or inspect a single repository by --slug, --id, or --name:

atlas cloud repo describe
atlas cloud repo describe --slug payments
Output
Slug payments
Title Payments
Type MIGRATION_DIRECTORY
URL atlas://payments
Driver mysql
Databases Synced 5
Databases Failed 0
Databases Pending 1

See Managing Repositories from the CLI for more.

Databases

atlas cloud database list shows your databases with their current version and sync status (SYNCED, PENDING, or FAILED), filterable by environment:

atlas cloud database list
atlas cloud database list --env-name production
Output
ID NAME ENV STATUS CURRENT VERSION
1 prod production SYNCED 20260514083000
2 prod-eu production PENDING 20260512141500
3 staging staging FAILED 20260515093000
--------------------------------
Page: 1 Page Size: 6 Total: 18

Inspect a single database by --id or --ext-id:

atlas cloud database describe
atlas cloud database describe --id 1
Output
ID 1
Name prod
Environment production
Status SYNCED
Current Version 20260514083000
Last Deployment Time 2026-05-14T08:30:00Z

Migrations

Each migrate apply or schema apply reported to the Registry is recorded as a migration event with a status (PASSED, FAILED, NO_ACTION, or DRY_RUN). List them, filtering by repository, status, environment, or database name:

atlas cloud migration list
atlas cloud migration list --repo payments --status PASSED
Output
ID REPO TYPE ENV DATABASE TARGETS VERSION STATUS
101 payments MIGRATION_DIRECTORY production prod - 20260514083000 PASSED
102 payments MIGRATION_DIRECTORY production (multiple) 8/8 20260514083000 PASSED
--------------------------------
Page: 1 Page Size: 6 Total: 18

Drill into a single event by --id; multi-target events (such as multi-tenant deployments) show (multiple) and a succeeded/total ratio:

atlas cloud migration describe
atlas cloud migration describe --id 102
Output
ID 102
Repository payments
Type MIGRATION_DIRECTORY
Database (multiple)
Version 20260514083000
Status PASSED
Completed At 2026-05-14T08:35:00Z
Targets 8/8 succeeded

See Inspecting Deployments from the CLI for more.

Scriptable Output

Every command supports --format with a Go template - including {{ json . }} for machine-readable JSON - and list commands are paginated with --page:

atlas cloud database list --format
atlas cloud database list \
--format '{{ range .Databases }}{{ .Name }} {{ .Status }}{{ "\n" }}{{ end }}'
Output
prod SYNCED
prod-eu PENDING
staging FAILED

Next Steps

See the CLI reference for the full set of commands, flags, and output fields.

featureatlas cloudregistryclideployment