forked from admin/brencher
docs(readme): add GITEA_TOKEN + Actions dispatch knobs to docker secret template
The brencher stack build-delegation pattern (see AGENTS.md) needs four
env vars to fire `GiteaActionsTrigger`:
- GITEA_TOKEN: Gitea PAT used to POST /dispatches and poll /runs
- WORKFLOW_REPO: owner/repo that hosts the workflow file (default: hermes/ansible)
- WORKFLOW_FILE: workflow filename (default: release.yml)
- WORKFLOW_REF: branch or tag the workflow is triggered on (default: master)
Without GITEA_TOKEN the trigger step gets HTTP 401 from
/api/v1/repos/{owner}/{repo}/actions/runs; the pipeline halts at
trigger_build and the stack never deploys. Added the missing keys to
the secret-create `printf` block in README.instruction.md so the next
person wiring up a brencher stack doesn't have to discover this.
Defaults shown match the connectivity_tester stack wiring
(admin/brencher#65).
This commit is contained in:
@@ -33,7 +33,7 @@ docker service update --secret-rm brencher-secrets brencher_brencher-backend
|
||||
docker service update --secret-rm brencher-secrets brencher2_brencher-backend
|
||||
docker secret rm brencher-secrets
|
||||
|
||||
printf "GIT_USERNAME=git\nGIT_PASSWORD=TODO\n" | \
|
||||
printf "GIT_USERNAME=git\nGIT_PASSWORD=TODO\nGITEA_TOKEN=TODO\nWORKFLOW_REPO=hermes/ansible\nWORKFLOW_FILE=release.yml\nWORKFLOW_REF=master\n" | \
|
||||
docker secret create brencher-secrets -
|
||||
|
||||
docker service update --secret-add brencher-secrets brencher_brencher-backend
|
||||
|
||||
Reference in New Issue
Block a user