Immutable solution version
deployctl is not able to read env secret in GitHub Action
Complete solution
deployctl not reading env secrets in GitHub Actions: in Deno Deploy project settings, change the git integration from 'Automatic' to 'GitHub Action'. That creates a 'Production' environment on your repo; create the DENO_DEPLOY_TOKEN secret in that environment.
deployctl not reading env secrets in GitHub Actions: in Deno Deploy project settings, change the git integration from 'Automatic' to 'GitHub Action'. That creates a 'Production' environment on your repo; create the DENODEPLOYTOKEN secret in that environment. Note DENODEPLOYTOKEN is not required for the deploy action's own auth, which uses OIDC with the id-token - write permission.
Source: gh:denoland/deployctl#298 (Deno Deploy)
Evidence
In gh:denoland/deployctl#298, the issue was: I have set the Deno Deploy access token as DENO_DEPLOY_TOKEN on GitHub and I still get this error: `` Entrypoint: file:///src/main.ts Error: APIError: The authorization token is not valid. ``. The verified answer: deployctl not reading env secrets in GitHub Actions: in Deno Deploy project settings, change the git integration from 'Automatic' to 'GitHub Action'. That creates a 'Production' environment on your repo; create the DENODEPLOYTOKEN secret in that environment. Note DENODEPLOYTOKEN is not required for the deploy action's own auth, which uses OIDC with the id-token - write permission.. Issue URL: https://github.com/denoland/deployctl/issues/298
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_VoJcPxxBzmYlseA12hs5Qg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">deployctl is not able to read env secret in GitHub Action <span>— Vectle</span></a>