CLI Reference
Introduction
This document serves as reference documentation for all available commands in the Atlas CLI.
Similar information can be obtained by running any atlas command with the -h
or --help
flags.
For a more detailed introduction to the CLI capabilities, head over to the Getting Started page.
Supported Version Policy
To ensure the best performance, security and compatibility with the Atlas Cloud service, the Atlas team
will only support the two most recent minor versions of the CLI. For example, if the latest version is
v0.31
, the supported versions will be v0.30
and v0.31
(in addition to any patch releases and the
"canary" release which is built twice a day).
Distributed Binaries
As part of our Supported Version Policy mentioned above, binaries for versions that were published more than 6 months ago will be removed from the CDN and Docker Hub.
The binaries and Docker images distributed in official releases are released in two flavors:
- Atlas - A binary built from the OSS repository in addition to proprietary code maintained by Ariga, including access to the Atlas Cloud service and commercial driver support. Atlas is distributed under the Atlas EULA.
- Atlas Community - A binary built from the OSS repository only. Atlas Community is distributed under the Apache 2 License.
For instructions on how to install Atlas Community, see this guide.
atlas ask
Use Atlas AI to resolve the latest error
Usage
atlas ask
atlas copilot
Start an interactive session with Atlas Copilot
Usage
atlas copilot [flags]
Flags
-c, --config string select config (project) file using URL format (default "file://atlas.hcl")
--env string set which env from the config file to use
-r, --resume string resume a session by providing an identifier
--var <name>=<value> input variables (default [])
atlas license
Display license information
Usage
atlas license
atlas login
Log in to Atlas Cloud.
Usage
atlas login [org] [flags]
Details
'atlas login' authenticates the CLI against Atlas Cloud.
Flags
--token string API token to authenticate to an Atlas Cloud organization
--format string output format
atlas logout
Logout from Atlas Cloud.
Usage
atlas logout
Details
'atlas logout' removes locally-stored credentials.
atlas migrate
Manage versioned migration files
Usage
atlas migrate
Details
'atlas migrate' wraps several sub-commands for migration management.
Flags
-c, --config string select config (project) file using URL format (default "file://atlas.hcl")
--env string set which env from the config file to use
--var <name>=<value> input variables (default [])
atlas migrate apply
Applies pending migration files on the connected database.
Usage
atlas migrate apply [flags] [amount]
Details
'atlas migrate apply' reads the migration state of the connected database and computes what migrations are pending. It then attempts to apply the pending migration files in the correct order onto the database. The first argument denotes the maximum number of migration files to apply. As a safety measure 'atlas migrate apply' will abort with an error, if:
- the migration directory is not in sync with the 'atlas.sum' file
- the migration and database history do not match each other
If run with the "--dry-run" flag, atlas will not execute any SQL.
Example
atlas migrate apply -u "mysql://user:pass@localhost:3306/dbname"
atlas migrate apply --dir "file:///path/to/migration/directory" --url "mysql://user:pass@localhost:3306/dbname" 1
atlas migrate apply --env dev 1
atlas migrate apply --dry-run --env dev 1
Flags
-u, --url string [driver://username:password@address/dbname?param=value] select a resource using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--format string Go template to use to format the output
--revisions-schema string name of the schema the revisions table resides in
--dry-run print SQL without executing it
--lock-timeout duration set how long to wait for the database lock (default 10s)
--baseline string start the first migration after the given baseline version
--tx-mode string set transaction mode [none, file, all] (default "file")
--exec-order string set file execution order [linear, linear-skip, non-linear] (default "linear")
--allow-dirty allow start working on a non-clean database
atlas migrate checkpoint
Generate a checkpoint file representing the state of the migration directory.
Usage
atlas migrate checkpoint [flags] [tag]
Details
The 'atlas migrate checkpoint' command uses the dev-database to calculate the current state of the migration directory by executing its files. It then creates a checkpoint file that represents this state, enabling new environments to bypass previous files and immediately skip to this checkpoint when executing the 'atlas migrate apply' command.
Example
atlas migrate checkpoint --dev-url docker://mysql/8/dev
atlas migrate checkpoint --dev-url "docker://postgres/15/dev?search_path=public"
atlas migrate checkpoint --dev-url "sqlite://dev?mode=memory"
atlas migrate checkpoint --env dev --format '{{ sql . " " }}'
Flags
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
-s, --schema strings set schema names
--lock-timeout duration set how long to wait for the database lock (default 10s)
--format string Go template to use to format the output
--qualifier string qualify tables with custom qualifier when working on a single schema
--edit edit the generated migration file(s)
atlas migrate diff
Compute the diff between the migration directory and a desired state and create a new migration file.
Usage
atlas migrate diff [flags] [name]
Details
The 'atlas migrate diff' command uses the dev-database to calculate the current state of the migration directory by executing its files. It then compares its state to the desired state and create a new migration file containing SQL statements for moving from the current to the desired state. The desired state can be another another database, an HCL, SQL, or ORM schema. See: https://atlasgo.io/versioned/diff
Example
atlas migrate diff --dev-url "docker://mysql/8/dev" --to "file://schema.hcl"
atlas migrate diff --dev-url "docker://postgres/15/dev?search_path=public" --to "file://atlas.hcl" add_users_table
atlas migrate diff --dev-url "mysql://user:pass@localhost:3306/dev" --to "mysql://user:pass@localhost:3306/dbname"
atlas migrate diff --env dev --format '{{ sql . " " }}'
Flags
--to strings [driver://username:password@address/dbname?param=value] select a desired state using the URL format
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
-s, --schema strings set schema names
--lock-timeout duration set how long to wait for the database lock (default 10s)
--format string Go template to use to format the output
--qualifier string qualify tables with custom qualifier when working on a single schema
--edit edit the generated migration file(s)
atlas migrate down
Reverting applied migration files from the database
Usage
atlas migrate down [flags] [amount]
Example
atlas migrate down -u "mysql://user:pass@localhost:3306/dbname"
atlas migrate down --env prod --to-version 20230102150405
atlas migrate down --env prod --to-tag e29be4e
Flags
-u, --url string [driver://username:password@address/dbname?param=value] select a resource using the URL format
--to-version string desired version to revert to
--to-tag string desired tag to revert to
--dir string select migration directory using URL format (default "file://migrations")
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--format string Go template to use to format the output
--dry-run print SQL without executing it
--revisions-schema string name of the schema the revisions table resides in
--lock-timeout duration set how long to wait for the database lock (default 10s)
atlas migrate edit
Edit a migration file by its name or version and update the atlas.sum file.
Usage
atlas migrate edit [flags] {name | version}
Example
atlas migrate edit 20060102150405
atlas migrate edit 20060102150405 --env dev
atlas migrate edit 20060102150405_name.sql --dir file://migrations
Flags
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
atlas migrate hash
Hash (re-)creates an integrity hash file for the migration directory.
Usage
atlas migrate hash [flags]
Details
'atlas migrate hash' computes the integrity hash sum of the migration directory and stores it in the atlas.sum file. This command should be used whenever a manual change in the migration directory was made.
Example
atlas migrate hash
Flags
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
atlas migrate import
Import a migration directory from another migration management tool to the Atlas format.
Usage
atlas migrate import [flags]
Example
atlas migrate import --from "file:///path/to/source/directory?format=liquibase" --to "file:///path/to/migration/directory"
Flags
--from string select migration directory using URL format (default "file://migrations")
--to string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
atlas migrate lint
Run analysis on the migration directory
Usage
atlas migrate lint [flags]
Example
atlas migrate lint --env dev
atlas migrate lint --dir "file:///path/to/migrations" --dev-url "docker://mysql/8/dev" --latest 1
atlas migrate lint --dir "file:///path/to/migrations" --dev-url "mysql://root:pass@localhost:3306" --git-base master
atlas migrate lint --dir "file:///path/to/migrations" --dev-url "mysql://root:pass@localhost:3306" --format '{{ json .Files }}'
Flags
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--format string Go template to use to format the output
--latest uint run analysis on the latest N migration files
--git-base string run analysis against the base Git branch
--git-dir string path to the repository working directory (default ".")
-w, --web open the lint report in the browser
atlas migrate ls
List all migration files in the directory.
Usage
atlas migrate ls [flags]
Example
atlas migrate ls
atlas migrate ls --dir file://migrations
atlas migrate ls --dir atlas://repo-name
Flags
--dir string select migration directory using URL format (default "file://migrations")
atlas migrate new
Creates a new empty migration file in the migration directory.
Usage
atlas migrate new [flags] [name]
Details
'atlas migrate new' creates a new migration according to the configured formatter without any statements in it.
Example
atlas migrate new my-new-migration
Flags
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--edit edit the created migration file(s)
atlas migrate push
Push a migration directory with an optional tag to the Atlas Registry
Usage
atlas migrate push [flags] directory[:tag]
Details
The 'atlas migrate push' command allows you to push your migration directory to the Atlas Registry. If no repository exists in the registry for the pushed directory, a new one is created. Otherwise, the directory state will be updated. Read more: https://atlasgo.io/registry
Example
atlas migrate push --dev-url docker://mysql/8/dev app
atlas migrate push --env dev app:latest
Flags
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--lock-timeout duration set how long to wait for the database lock (default 10s)
--tag string tag to push the directory with
atlas migrate rebase
Rebase one or more migration file on top of all other files and update the atlas.sum file.
Usage
atlas migrate rebase [flags] {name | version}...
Example
atlas migrate rebase 20060102150405
atlas migrate rebase 20060102150405 --env dev
atlas migrate rebase 20060102150405_name.sql --dir file://migrations
atlas migrate rebase 20060102150405...20060102150407
Flags
--dir string select migration directory using URL format (default "file://migrations")
atlas migrate rm
Remove a migration file from the migration directory. Does not work for remote directories.
Usage
atlas migrate rm [flags] [amount]
Example
atlas migrate rm
atlas migrate rm --env local 20060102150405
atlas migrate rm --env local 20060102150405_name.sql
Flags
--dir string select migration directory using URL format (default "file://migrations")
atlas migrate set
Set the current version of the migration history table.
Usage
atlas migrate set [flags] [version]
Details
'atlas migrate set' edits the revision table to consider all migrations up to and including the given version to be applied. This command is usually used after manually making changes to the managed database.
Example
atlas migrate set 3 --url "mysql://user:pass@localhost:3306/"
atlas migrate set --env local
atlas migrate set 1.2.4 --url "mysql://user:pass@localhost:3306/my_db" --revision-schema my_revisions
Flags
-u, --url string [driver://username:password@address/dbname?param=value] select a resource using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--revisions-schema string name of the schema the revisions table resides in
atlas migrate show
Show the contents of one or more migration files.
Usage
atlas migrate show [flags] {name | version}...
Example
atlas migrate show 20060102150405 20060702151900
atlas migrate show 20060102150405_add_users.sql
atlas migrate show 20060102150405 --dir atlas://repo
atlas migrate show 20060102150405_name.sql --env dev
Flags
--dir string select migration directory using URL format (default "file://migrations")
atlas migrate status
Get information about the current migration status.
Usage
atlas migrate status [flags]
Details
'atlas migrate status' reports information about the current status of a connected database compared to the migration directory.
Example
atlas migrate status --url "mysql://user:pass@localhost:3306/"
atlas migrate status --url "mysql://user:pass@localhost:3306/" --dir "file:///path/to/migration/directory"
Flags
-u, --url string [driver://username:password@address/dbname?param=value] select a resource using the URL format
--format string Go template to use to format the output
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--revisions-schema string name of the schema the revisions table resides in
atlas migrate test
Run migration tests against the given directory
Usage
atlas migrate test [flags] [paths]
Example
atlas migrate test --dev-url docker://mysql/8/dev --dir file://migrations .
atlas migrate test --env dev ./tests
Flags
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
--revisions-schema string name of the schema the revisions table resides in
--run string run only tests matching regexp
atlas migrate validate
Validates the migration directories checksum and SQL statements.
Usage
atlas migrate validate [flags]
Details
'atlas migrate validate' computes the integrity hash sum of the migration directory and compares it to the atlas.sum file. If there is a mismatch it will be reported. If the --dev-url flag is given, the migration files are executed on the connected database in order to validate SQL semantics.
Example
atlas migrate validate
atlas migrate validate --dir "file:///path/to/migration/directory"
atlas migrate validate --dir "file:///path/to/migration/directory" --dev-url "docker://mysql/8/dev"
atlas migrate validate --env dev --dev-url "docker://postgres/15/dev?search_path=public"
Flags
--dev-url string [driver://username:password@address/dbname?param=value] select a dev database using the URL format
--dir string select migration directory using URL format (default "file://migrations")
--dir-format string select migration file format (default "atlas")
atlas schema
Work with atlas schemas.
Usage
atlas schema
Details
The atlas schema
command groups subcommands working with declarative Atlas schemas.
Flags
-c, --config string select config (project) file using URL format (default "file://atlas.hcl")
--env string set which env from the config file to use
--var <name>=<value> input variables (default [])
atlas schema apply
Apply an atlas schema to a target database.