garage v2.2.0 [features: bundled-libs, consul-discovery, fjall, journald, k2v, kubernetes-discovery, lmdb, metrics, sqlite, syslog, telemetry-otlp] Structure for secret values or paths that are passed as CLI arguments or environment variables, instead of in the config file USAGE: garage [OPTIONS] FLAGS: --help Prints help information -V, --version Prints version information OPTIONS: --admin-token Admin API authentication token, replaces admin.admin_token in config.toml when running the Garage daemon [env: GARAGE_ADMIN_TOKEN=] --admin-token-file Admin API authentication token file path, replaces admin.admin_token in config.toml and admin-token when running the Garage daemon [env: GARAGE_ADMIN_TOKEN_FILE=] --allow-world-readable-secrets Skip permission check on files containing secrets [env: GARAGE_ALLOW_WORLD_READABLE_SECRETS=] -c, --config Path to configuration file [env: GARAGE_CONFIG_FILE=] [default: /etc/garage.toml] --metrics-token Metrics API authentication token, replaces admin.metrics_token in config.toml when running the Garage daemon [env: GARAGE_METRICS_TOKEN=] --metrics-token-file Metrics API authentication token file path, replaces admin.metrics_token in config.toml and metrics-token when running the Garage daemon [env: GARAGE_METRICS_TOKEN_FILE=] -h, --rpc-host Host to connect to for admin operations, in the format: @: [env: GARAGE_RPC_HOST=] -s, --rpc-secret RPC secret network key, used to replace rpc_secret in config.toml when running the daemon or doing admin operations [env: GARAGE_RPC_SECRET=] --rpc-secret-file RPC secret network key, used to replace rpc_secret in config.toml and rpc-secret when running the daemon or doing admin operations [env: GARAGE_RPC_SECRET_FILE=] SUBCOMMANDS: admin-token Operations on admin API tokens block Low-level node-local debug operations on data blocks bucket Operations on buckets convert-db Convert metadata db between database engine formats help Prints this message or the help of the given subcommand(s) json-api Directly invoke the admin API using a JSON payload. The result is printed to `stdout` in JSON format key Operations on S3 access keys layout Operations on the assignment of node roles in the cluster layout meta Operations on the metadata db node Operations on individual Garage nodes offline-repair Offline reparation of node data (these repairs must be run offline directly on the server node) repair Start repair of node data on remote node server Run Garage server stats Gather node statistics status Get network status worker Manage background workers