Token issues with Vercel promote (team scope)

[mikedidomizio]

Question

Hey there,

I'm trying to promote a build to production and receive issues whether I'm going through CLI or CURL.

I'm guessing it's the scoping of my Vercel tokens with my team.

I create a token with scope being the team I'm on

$ npx vercel@31.0.1 promote https://*********.vercel.app/ --token=$VERCEL_TOKEN
Vercel CLI 31.0.1
> Fetching deployment "https://*********.vercel.app/" in mikedidomizio…
Error: Deployment belongs to a different team

The scope of the token was for that team, but I tried the Full Account access as well, same thing.

I tried via CURL with the team scoped token and the response I get

{
    "error": {
        "code": "forbidden",
        "message": "Not authorized: Trying to access resource under scope \"mikedidomizio\". You must re-authenticate to this scope or use a token with access to this scope.",
        "saml": true,
        "teamId": null,
        "scope": "mikedidomizio",
        "enforced": false
    }
}

with teamId being null, and scope being "mikedidomizio". Is it telling me the token isn't set up correctly?

If I try with a Full Account token, I get the following

{
    "error": {
        "code": "deployment_not_found",
        "message": "Deployment not found"
    }
}

This might be closer, if I try to List Deployments though, all I get is my personal account deploys and not any of my team.

Anyways, somewhere I've done something incorrectly. Everything else works via CLI/CURL, it's just the promote I'm having issues with.

[mikedidomizio]

Closing, the issue was not passing the --scope=TEAM_ID