vexa_smoke.py - Vexa Delivery

Source: kit/smoke/vexa_smoke.py · audience: customer

When you use this

Run after an install or an upgrade to prove the release worked HERE: the pods that should be running are, and — with --flows — a bot joined a real meeting and produced transcript segments. The receipt it writes is what turns “it synced” into “it works”.

Usage

Emitted from python3 kit/smoke/vexa_smoke.py --help.

usage: vexa_smoke.py [-h] [--namespace NAMESPACE] [--kubeconfig KUBECONFIG]
                     [--release-prefix RELEASE_PREFIX] [--customer-values CUSTOMER_VALUES]
                     [--admin-token ADMIN_TOKEN] [--flows] [--flows-key FLOWS_KEY]
                     [--meeting-url MEETING_URL] [--operator-email OPERATOR_EMAIL]
                     [--admit-timeout ADMIT_TIMEOUT] [--min-segments MIN_SEGMENTS]
                     [--non-interactive]

options:
  -h, --help            show this help message and exit
  --namespace NAMESPACE
  --kubeconfig KUBECONFIG
  --release-prefix RELEASE_PREFIX
                        componentName prefix (release 'vexa' → vexa-vexa)
  --customer-values CUSTOMER_VALUES
                        read admin token / flows key from this values file
  --admin-token ADMIN_TOKEN
  --flows
  --flows-key FLOWS_KEY
  --meeting-url MEETING_URL
  --operator-email OPERATOR_EMAIL
  --admit-timeout ADMIT_TIMEOUT
  --min-segments MIN_SEGMENTS
  --non-interactive