# Env for the real-deployment tests (see vercel-deploy.test.ts) — run via: # varlock run --path ./deploy -- ... # In CI, OP_CI_TOKEN is injected and takes precedence; locally (no token) the # 1Password desktop app is used. (Local runs can also skip varlock entirely — # the helpers fall back to your `vercel login`.) # # @defaultSensitive=false @defaultRequired=infer # @plugin(@varlock/1password-plugin) # @initOp(token=$OP_CI_TOKEN, allowAppAuth=not($VARLOCK_IS_CI)) # --- # True when running in CI (auto-detected). Declared explicitly so it resolves as # a graph item (available early enough to gate the @initOp app-auth fallback). # @type=boolean VARLOCK_IS_CI= # 1Password service account token. Injected in CI (GitHub Actions secret). # @type=opServiceAccountToken @sensitive OP_CI_TOKEN= # Auth for the varlockdev Vercel account that owns the varlock-deploy-test project # @sensitive VERCEL_TOKEN=op("op://VarlockCI/vercel/VERCEL_TOKEN") # Scoping for non-interactive vercel CLI usage (read natively by the CLI from # env — avoids the interactive team/project prompts in CI). These identify the # throwaway varlock-deploy-test project under the varlockdev account. VERCEL_ORG_ID=team_2H8WtheUOme2pvzwygblZ0F7 VERCEL_PROJECT_ID=prj_yBS7T80PAKTQji0LivxJrV58GC3j