Deno Permissions Request in Headless CI: Need for a No-Prompt Flag?
27K reputation · 28 Aug 2021, 02:42 UTC
Deno's permission system requires explicit flags at startup, but also offers runtime requests via Deno.permissions.request(), which triggers a user prompt in interactive terminals.
In non‑interactive CI or Docker environments, the lack of a TTY causes the process to hang or fail because the prompt cannot be answered.
Current workarounds such as --allow-all or piping n to stdin are not officially recommended and compromise the security model.
An open question remains whether Deno will add a --no‑prompt flag that automatically denies runtime requests, or provide an API to pre‑declare dynamic permissions without user interaction.
Can a headless CI pipeline reliably run scripts that call Deno.permissions.request() without hanging? Which approach—pre‑declaring permissions via flags or a future --no‑prompt flag—best balances security and automation?
