Skip to main content
Initialize a named store entry from profiles.yaml. This command resolves the store configuration and encryption credentials, checks backend access, and initializes the repository when the store is reachable but not yet initialized.

​
Usage

cloudstic store init [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.
​
-yes
boolean
default:"false"
Initialize without confirmation prompt.

​
Examples

# Initialize a named store
cloudstic store init prod-s3

# Initialize non-interactively
cloudstic store init -yes prod-s3

# Use a custom profiles file
cloudstic store init -profiles-file ~/.config/cloudstic/profiles.yaml prod-s3

​
Common outcomes

  • Store already initialized: command confirms access and (for encrypted repos) verifies configured unlock credentials.
  • Store reachable but not initialized: command initializes repository metadata.
  • Missing/invalid credentials: command returns a clear error for secret resolution or unlock validation.

​
See Also