mirror of
https://scm.tikali.ai/tikali/applications/monky/monky-deployd.git
synced 2026-09-18 04:36:15 +00:00
feat(install): read-only deploy token for the private package registry (v0.1.2)
The GitLab project is private (its parent groups are private, so it cannot be made public): the v0.1.1 one-liner answered 401 anonymously. install.sh gains --token / MONKY_DEPLOYD_TOKEN and sends `DEPLOY-TOKEN: <token>` (a GitLab deploy token, scope read_package_registry only, revocable) on every registry download, the script itself included; the token goes through a 0600 curl -K file (never the command line, the log or an xtrace). The grant is taken via --bootstrap-file when the script is piped (stdin IS the script). Ansible: monky_deployd_download_token (vaulted) -> DEPLOY-TOKEN header, no_log. Docs explain why, the token's scope and the --source gitea alternative (split-horizon Gitea, cbs/iac#102). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KLB7jieMNRkTsJ2epr4Ds1
This commit is contained in:
+3
-2
@@ -10,8 +10,9 @@
|
||||
# GITEA_TOKEN — Gitea API token (write:repository) for `release:gitea`; without it the job is manual
|
||||
#
|
||||
# Release assets are published to BOTH the GitLab generic package registry (the installer's primary
|
||||
# source — the project is public; gitea.cbs.tikali.net is split-horizon inside the estate, cbs/iac#102)
|
||||
# and the Gitea mirror release (`install.sh --source gitea`, off-estate).
|
||||
# source — the project is PRIVATE (parent groups are private), so install.sh sends a read-only deploy
|
||||
# token (read_package_registry) as DEPLOY-TOKEN; gitea.cbs.tikali.net is split-horizon inside the
|
||||
# estate, cbs/iac#102) and the Gitea mirror release (`install.sh --source gitea`, off-estate).
|
||||
# GITLAB_TRANSLATE_TOKEN — used by the translate-docs component (group level)
|
||||
|
||||
include:
|
||||
|
||||
Reference in New Issue
Block a user