Skip to content

cloudtaser-cli source host-launch prepare

Prepare a proposed host approval from the reviewed authority file, this host's public machine/boot/account identity and a verified signed Port release. No administrator credential, source API, role, service or Kubernetes object is read or changed. Review the public JSON before passing it to host-launch; the launcher independently verifies the active graph, executable and actual process. The beacon tenant must already be enrolled with the relay and source.

Usage

cloudtaser-cli source host-launch prepare [flags]

Flags

Flag Type Default Required Description
--authority-file string (empty) no reviewed public authority approval used for provision/activate
--beacon-address string (empty) no registered beacon host:port
--beacon-ca-file string /etc/ssl/certs/ca-certificates.crt no absolute public beacon CA bundle path on this host
--beacon-tenant-id string (empty) no canonical public tenant ID already enrolled with the relay and source
--executable string /usr/local/libexec/cloudtaser-port no absolute signed Port executable path
--help, -h bool false no help for prepare
--lifetime duration 1h0m0s no maximum proposed launch lifetime; 2 minutes to 24 hours
--port-version string (empty) no exact managed cohort Port version; another version is refused
--secretstore-address string (empty) no canonical HTTPS source origin
--secretstore-ca-file string (empty) no absolute public source CA path on this host
--timeout duration 20m0s no maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)

All commands