Skip to main content
Validate one configured store from profiles.yaml. cloudstic store verify checks:
  • Credential resolution from configured secret refs (env://, keychain://, etc.)
  • Backend connectivity and basic access
  • For encrypted repositories: whether configured credentials can unlock the repository

​
Usage

cloudstic store verify [options] <name>
In interactive mode, if <name> is omitted, you’ll be prompted to select one.

​
Options

​
-profiles-file
string
Path to the profiles YAML file.

​
Examples

# Verify one store by name
cloudstic store verify prod-s3

# Verify using a custom profiles file
cloudstic store verify -profiles-file ~/.config/cloudstic/profiles.yaml prod-s3

​
What This Command Is (and Is Not)

  • Use store verify to validate configuration and access for a store entry.
  • Use cloudstic store init to initialize a configured store that is reachable but not yet initialized.
  • Use cloudstic check to validate repository integrity (reference graph and object/data correctness).

​
Common Outcomes

  • Missing env var / unavailable secret backend: configuration is valid, but current shell/session cannot resolve required credentials.
  • Wrong password/key for an initialized encrypted repo: store is reachable, but encryption credentials are invalid for unlock.
  • Connectivity/auth failures: credentials resolved, but backend access failed.

​
See Also