privacy-in-design/gitea-migration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add idempotent token deletion before generating new Gitea admin token

Browse Source
This commit is contained in:
S
2026-03-01 08:58:34 -05:00
parent 5bdf72063e
commit 83f706c6b8
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
phase1_gitea_unraid.sh
View File

@@ -129,6 +129,13 @@ if [[ -n "${GITEA_ADMIN_TOKEN:-}" ]]; then
fi fi
if [[ -z "${GITEA_ADMIN_TOKEN:-}" ]]; then if [[ -z "${GITEA_ADMIN_TOKEN:-}" ]]; then
# Delete any stale token with the same name (idempotent re-run safety).
# Gitea returns 409 Conflict if a token with this name already exists.
curl -sf -u "${GITEA_ADMIN_USER}:${GITEA_ADMIN_PASSWORD}" \
-X DELETE \
"${GITEA_INTERNAL_URL}/api/v1/users/${GITEA_ADMIN_USER}/tokens/migration-token" \
-o /dev/null 2>/dev/null || true
# Generate token using basic auth (username:password). # Generate token using basic auth (username:password).
# The .sha1 field in the response contains the full token — this is the # The .sha1 field in the response contains the full token — this is the
# ONLY time it's returned, so we must save it immediately. # ONLY time it's returned, so we must save it immediately.