Files
harmony/examples/sttest/env.sh
Sylvain Tremblay a906a51ef6 refactor(okd): rename AddOkdNodeScore to OKDAddNodeScore
Aligns with the rest of the OKD score namespace (OKDSetup01InventoryScore,
OKDBootstrap02…, OKDLoadBalancerScore, …). The Add prefix made this one
the odd name out. Renames the companion interpret (AddOkdNodeInterpret →
OKDAddNodeInterpret), the Score::name() debug string, and the
InterpretName::Custom tag for symmetry. AddNodeRole stays as-is (not a
Score, and its prefix still reads fine).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-21 15:41:40 -04:00

20 lines
876 B
Bash

export HARMONY_SECRET_NAMESPACE=sttest0
export HARMONY_SECRET_STORE=file
export HARMONY_DATABASE_URL=sqlite://harmony_sttest0.sqlite
export RUST_LOG=harmony=debug
# Two OPNsense credential pairs are required (both are Harmony Secrets and
# will be prompted for interactively on first run; the env vars below are
# here as a reminder for unattended runs):
# - OPNSenseFirewallCredentials (SSH username/password)
# - OPNSenseApiCredentials (API key/secret from System > Access >
# Users > API Keys)
#
# export OPNSENSE_PRIMARY_API_KEY="..."
# export OPNSENSE_PRIMARY_API_SECRET="..."
# After the install pipeline finishes, OKDAddNodeScore needs a reachable
# cluster. Point KUBECONFIG at the kubeconfig that `openshift-install`
# wrote during bootstrap, e.g.:
# export KUBECONFIG=./data/okd/installation_files_sttest0/auth/kubeconfig