Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deployctl deploy with --org parameter fails with Access Denied when using an org-scoped token #305

Open
NReilingh opened this issue Apr 16, 2024 · 0 comments

Comments

@NReilingh
Copy link

NReilingh commented Apr 16, 2024

When using an org-scoped deploy token, the --org parameter is superfluous since the org token will only have access to its one org. However, providing this parameter with the org name matching the token currently results in error: Access Denied. I have only tested this with an org name that has spaces.

Repro:

  • Create org "My Org Name"
  • Create access token for this org and export it as DENO_DEPLOY_TOKEN in a shell.
  • Run deployctl deploy --org="My Org Name"

Expected outcome:

Command proceeds as the token has access to the specified org.

Actual outcome:

Command fails with Access Denied when fetching org details:

% mkdir -p /tmp/wat; cd /tmp/wat
% deno init
% deployctl deploy --org="My Org Name"
i Using config file '/private/tmp/wat/deno.json'
‼ No project name or ID provided with either the --project arg or a config file.
⠸ You have specified the organization My Org Name. Fetching details...
error: Access Denied
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant