← All questions

Unresolved variable ${API_TOKEN} at "env.api.auth.token" — where is it supposed to look?

api:
  baseUrl: https://jsonplaceholder.typicode.com
  auth: { type: bearer, token: "${API_TOKEN}" }

sdods run -p demo-shop -e staging -l api

✖ CONFIG_UNRESOLVED_VAR: Unresolved variable ${API_TOKEN} at "env.api.auth.token".
  hint: Add API_TOKEN=... to .env or .env.<env> (repo root or project folder), or export it in the shell.
  docs: https://docs.sdods.com/docs/guides/configuration

2 answers

• 58votes✓

  Accepted answer

  The file name. env.staging is not a name SDODS looks for — the leading dot is part of it.

  For each of two roots (the repo root first, then the project folder) SDODS reads these four names, in this order:

  • .env
  • .env.<env>
  • .env.local
  • .env.<env>.local

  So for -e staging inside projects/demo-shop that is up to eight files, missing ones skipped. Rename yours to projects/demo-shop/.env.staging and the run gets past resolution.

  The check itself is not clever: after every layer has merged, the whole tree is walked and any ${VAR} that has no value and no default throws with the dotted path it sat on. env.api.auth.token is telling you exactly which leaf to look at.

  RNanswered by Reeta Nandalmaintainer41,280 · 6 Oct 2020
• 11votes

  Worth adding: exporting it in the shell also works and, if you do both, the shell wins.

  bashCopy

  API_TOKEN=abc123 sdods run -p demo-shop -e staging -l api

  We keep the real one out of the tree entirely and only commit a .env.example listing the names, which is what the generated project scaffolds anyway.

  MKanswered by Marijn Kuiper18,840 · 9 Oct 2020