2
0

fix(ci): use authenticated clone for private vault repository
Some checks failed
Build and Release / Build Binaries (amd64, darwin, macos) (push) Has been cancelled
Build and Release / Build Binaries (amd64, linux, linux-latest) (push) Has been cancelled
Build and Release / Build Binaries (amd64, windows, windows-latest) (push) Has been cancelled
Build and Release / Build Binaries (arm64, darwin, macos) (push) Has been cancelled
Build and Release / Build Binary (linux/arm64) (push) Has been cancelled
Build and Release / Create Release (push) Has been cancelled
Build and Release / Integration Tests (PostgreSQL) (push) Has been cancelled
Build and Release / Lint (push) Has been cancelled
Build and Release / Unit Tests (push) Has been cancelled

Add VAULT_TOKEN environment variable to vault sync steps and use token-based authentication when cloning gitcaddy-vault repository. Falls back to unauthenticated clone if token is not provided.

This enables CI builds to access the private vault repository using the RELEASE_TOKEN secret.
This commit is contained in:
2026-01-27 23:32:39 -05:00
parent 8806fcecba
commit cd47462df1
2 changed files with 12 additions and 2 deletions

View File

@@ -15,7 +15,11 @@ if [ -z "$VAULT_PATH" ]; then
VAULT_PATH=$(mktemp -d)
CLEANUP_VAULT=true
echo "Cloning gitcaddy-vault to $VAULT_PATH..."
git clone --depth 1 https://git.marketally.com/gitcaddy/gitcaddy-vault.git "$VAULT_PATH"
if [ -n "${VAULT_TOKEN:-}" ]; then
git clone --depth 1 "https://token:${VAULT_TOKEN}@git.marketally.com/gitcaddy/gitcaddy-vault.git" "$VAULT_PATH"
else
git clone --depth 1 https://git.marketally.com/gitcaddy/gitcaddy-vault.git "$VAULT_PATH"
fi
else
CLEANUP_VAULT=false
echo "Using vault from $VAULT_PATH"