Skip to main content

atmos store list

List the store backends configured under stores: in atmos.yaml. For each backend, this command shows its kind. It also shows whether the backend is a secret backend. It also shows which optional capabilities the backend supports, such as deletion, key enumeration, or a local existence check. Pass a STORE name to list the key/value pairs stored inside that backend instead, scoped with --stack and --component the same way store set writes a key. Only backends that support key enumeration can list their contents this way — check the Listable column first.

atmos store list --help

Usage​

atmos store list [STORE] [flags]

Examples​

# List all configured store backends
atmos store list

# Pipeline-friendly output
atmos store list --format=json

# List the key/value pairs in a store, scoped to a stack and component
atmos store list app-metadata --stack=prod --component=ecs-service

# List store-global key/value pairs (no --stack/--component)
atmos store list app-metadata

Arguments​

STORE

Optional. The name of a configured store backend. When set, this command lists the key/value pairs stored inside that backend instead of the configured backends themselves.

Flags​

--stack (alias -s)

Only used with STORE. The Atmos stack used to scope the listing. This flag is optional. It must match the value used with set.

Environment variable: ATMOS_STACK

--component (alias -c)

Only used with STORE. The Atmos component used to scope the listing. This flag is optional. It must match the value used with set.

Environment variable: ATMOS_COMPONENT

--identity (alias -i)

Only used with STORE. The identity Atmos uses to access the store backend.

Environment variable: ATMOS_IDENTITY

--format (alias -f)

The output format. Choices are table, json, yaml, csv, or tsv. On a terminal, the default is a styled table. When piped, the default is plain, delimited output.

Values Are Masked​

When you list a store's contents, Atmos masks every value the same way atmos store get does. A value from a secret: true store — or any value that happens to look like a credential — shows as a masked placeholder. Pass --mask=false to reveal the real values.

Backend Support​

Not every store backend can enumerate its keys. 1Password cannot list keys, because its references are opaque and do not follow a predictable naming pattern. The default system keychain backend cannot list keys either, because the underlying OS keychain APIs do not support enumeration. The file and memory keychain backends do support it.

Every other supported backend supports key enumeration: AWS SSM, AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, GCP Secret Manager, Redis, Artifactory, and GitHub Actions.

See Also​