Add ExternalSecret for ISSUE_CORE_API_KEY on Railiance
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:
parent
7dab19b0d7
commit
9a7ae8b59a
7 changed files with 128 additions and 20 deletions
|
|
@ -37,9 +37,8 @@ if ! secret_exists actcore-runtime-secret; then
|
|||
--from-literal=ACTCORE_DB_URL="$ACTCORE_DB_URL" \
|
||||
--from-literal=WEBHOOK_SECRET_GITEA="" \
|
||||
--from-literal=WEBHOOK_SECRET_GITHUB="" \
|
||||
--from-literal=OPS_HUB_KEY="" \
|
||||
--from-literal=ISSUE_CORE_API_KEY=""
|
||||
--from-literal=OPS_HUB_KEY=""
|
||||
fi
|
||||
# When promoting live task emission, patch ISSUE_CORE_API_KEY on
|
||||
# actcore-runtime-secret to match issue-core's runtime secret. Never commit the
|
||||
# value; use the OpenBao lane documented in issue-core-ingestion-api-key.
|
||||
# ISSUE_CORE_API_KEY is merged into actcore-runtime-secret by ExternalSecret
|
||||
# actcore-issue-core-runtime (k8s/railiance/15-externalsecret-issue-core.yaml).
|
||||
# Apply that manifest after ClusterSecretStore openbao-activity-core is Ready.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue