cloudtaser-cli source verify-plan

Reads a MigrationPlan YAML file and checks each secret mapping against the secret store.

For each secret mapping the command checks: 1. The secret store path exists 2. The path has data (values populated) 3. The fields listed in the mapping exist in the secret store data

This is a read-only operation. Use it after populating secret values to confirm everything is ready before running "target protect --plan".

Usage

cloudtaser-cli source verify-plan [plan.yaml] [flags]

Examples

# Verify a plan
  cloudtaser-cli source verify-plan plan.yaml \
    --secretstore-address https://bao.example.com:8200 \
    --ca-cert ./source-ca.pem --secretstore-token-file ./private-bootstrap.token

Flags

Flag	Type	Default	Required	Description
--ca-cert	string	(empty)	no	alias for --secretstore-ca-file (verified private-CA trust)
--help, -h	bool	false	no	help for verify-plan
--secretstore-address	string	(empty)	no	secret store address (required; env: CLOUDTASER_SECRETSTORE_ADDRESS, VAULT_ADDR)
--secretstore-ca-file	string	(empty)	no	PEM CA bundle for verified secret-store TLS (env: VAULT_CACERT)
--secretstore-token	string	(empty)	no	secretstore token
--secretstore-token-file	string	(empty)	no	path to file containing token, or '-' for stdin
--timeout	duration	20m0s	no	maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)

All commands