Hello,

Could you share the link of the project?

Hi

This one? https://vercel.com/pistachiosoftware/pistachio-app

Hi @leonardofaria, can you share the purpose for pulling down the variables? Because if it is for running your app locally than I think a better command for doing this is: vercel env pull --environment=app2.

But if you plan to use them for vercel build or vercel dev then yes vercel pull --yes --environment=app2 --token=$VERCEL_TOKEN is the correct one.

I tried these for my project and it worked as expected:

• the first one generated a .env.local at the project root
• the second one generate a .env.staging.local in the .vercel/ folder (staging is the name of my custom environment)

I hope this helps.

I would like to build app2 (branch app2) and production (branch main) in GHA.

As I mentioned before the pull command is not building several variables. For example I would expect 4 env variables starting with TYPESENSE and some starting with GOOGLE. Can you see them in your file pulled file?

Thank you

I see. I think both commands worked for me. I tested by creating a custom environment called staging then added a few environment variables to my project: 1 to all environments, 1 to only staging, and 1 to all except staging. In this case, when I ran the commands I got the 2 environment variables added to the local file as expected.

Can you try recreating this scenario as I said? And maybe run it on your system so we can confirm quickly.

Found the issue!

When I run vercel link it linked to pistachiosoftware/pistachioapp however the correct is pistachiosoftware/pistachio-app. Pull would always fail since the name of the project was wrong. The solution was replying no in the Found project “pistachiosoftware/pistachio”. Link to it?. I was not expecting that because my vercel.json already had the teamId and projectId properly assigned.

1
vercel link
2
Vercel CLI 41.7.2
3
? Set up “~/Sites/pistachio”? yes
4
? Which scope should contain your project? Pistachio
5
? Found project “pistachiosoftware/pistachio”. Link to it? no
6
? Link to different existing project? yes
7
? What’s the name of your existing project? pistachio-app

Hi @leonardofaria, so glad you got this working.

Can you share the vercel.json file. Because, I think after linking the project Vercel CLI stores this info in .vercel/ directory, which might not be available because it's excluded in source control.

Here it is

1
{
2
  "$schema": "https://openapi.vercel.sh/vercel.json",
3
  "buildCommand": "pnpm build",
4
  "installCommand": "pnpm install --frozen-lockfile",
5
  "git": {
6
    "deploymentEnabled": {
7
      "main": false,
8
      "preview": true,
9
      "app2": false
10
    }
11
  },
12
  "headers": [
13
  ],
14
  "crons": [
15
  ],
16
  "functions": {
17
    "app/api/**/*": {
18
      "maxDuration": 300
19
    }
20
  }
21
}

I removed the content of headers and crons to make the code smaller.

I think this vercel.json is still working because the crons are working, the headers are there and the git settings are working

Thanks @leonardofaria. It makes sense. As I said before, after linking the project Vercel CLI stores this info in .vercel/ directory, which might not be available because it’s excluded in source control.