cloudtaser-cli source status

Connects to the OpenBao instance and reports its health status, seal state, and cluster information.

If a token is provided, additional checks are performed: - List enabled auth methods - List enabled secret engines - Check Kubernetes auth method configuration

Usage

cloudtaser-cli source status [flags]

Examples

# Basic health check (run on the secretstore VM, defaults to localhost)
  cloudtaser-cli source status

  # Override the address (e.g. when running against a remote vault)
  cloudtaser-cli source status --secretstore-address https://vault.eu.example.com

  # Health check with auth details
  cloudtaser-cli source status --secretstore-token-file /etc/cloudtaser/admin.token

Flags

Flag	Type	Default	Required	Description
--help, -h	bool	false	no	help for status
--secretstore-address	string	http://127.0.0.1:8200	no	secret store address (defaults to http://127.0.0.1:8200 — the local OpenBao systemd service on the secretstore VM; env: CLOUDTASER_SECRETSTORE_ADDRESS, VAULT_ADDR)
--secretstore-allow-insecure	bool	false	no	allow explicitly requested insecure secret store TLS options (development only)
--secretstore-ca-file	string	(empty)	no	PEM CA bundle for verified secret-store TLS (env: VAULT_CACERT)
--secretstore-skip-verify	bool	false	no	skip secret store TLS certificate verification (requires --secretstore-allow-insecure; development only)
--secretstore-token	string	(empty)	no	secret store token (prefer --secretstore-token-file or SECRETSTORE_TOKEN to avoid process-list exposure)
--secretstore-token-file	string	(empty)	no	path to a file containing the secret store token, or '-' to read it from stdin
--timeout	duration	20m0s	no	maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)

All commands