⚠️ DEPRECATED: Setup GitOps Personal Access Token (PAT)¶
This document is DEPRECATED as of 2025-11-21.
Use instead: Setup GitOps GitHub App Authentication
Why This is Deprecated¶
The CI/CD workflow (ci-cd.yml) now uses GitHub App authentication instead of Personal Access Tokens.
The workflow uses:
APP_IDsecret (GitHub App ID)APP_PRIVATE_KEYsecret (GitHub App private key)
Not:
❌ No longer usedGITOPS_PAT(Personal Access Token)
Migration Required¶
If you previously set up GITOPS_PAT:
- Read new guide: setup-gitops-github-app.md
- Create GitHub App with appropriate permissions
- Add secrets:
APP_IDandAPP_PRIVATE_KEYto syrf repository - Test: Verify promotion workflow works
- Clean up: Delete
GITOPS_PATsecret and revoke the PAT
Why GitHub App is Better¶
| Feature | GitHub App ✅ | PAT |
|---|---|---|
| Scoped to specific repos | ✅ Yes | ❌ No |
| Organization identity | ✅ Yes | ❌ No (tied to user) |
| No expiration | ✅ Yes | ❌ Requires rotation |
| Better audit trail | ✅ Yes | ⚠️ Mixed with user activity |
| Survives user leaving | ✅ Yes | ❌ No |
For current setup instructions, see: Setup GitOps GitHub App Authentication