Add ExternalSecret for ISSUE_CORE_API_KEY on Railiance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 6s
Build and Publish Container Image / build-and-push (push) Successful in 13s

Sync the shared issue-core ingestion key from OpenBao into
actcore-runtime-secret via External Secrets, with an interim coulombcore
ClusterSecretStore bootstrap script and deploy docs. Removes manual key
injection from bootstrap-secrets.sh.
This commit is contained in:
tegwick 2026-07-08 00:04:38 +02:00
parent 7dab19b0d7
commit 9a7ae8b59a
7 changed files with 128 additions and 20 deletions

View file

@ -60,6 +60,9 @@ railiance-up: ## Build image and start full railiance stack (no Elasticsearch)
railiance-down: ## Stop and remove railiance stack containers
docker compose -f docker-compose.railiance.yml down
openbao-eso-token-apply: ## Mint coulombcore OpenBao ESO token for railiance01 activity-core
OPENBAO_TOKEN_FILE="$(HOME)/.local/openbao/platform-admin.token" bash scripts/openbao-eso-token-apply.sh
# ── Local dev processes ───────────────────────────────────────────────────────
start-worker: ## Start Temporal worker (reads env from .env if present)