← All questions

Environment "qa" is not in envs.available [local, staging] — I created envs/qa.yaml already

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

✖ ENV_NOT_FOUND: Environment "qa" is not in envs.available [local, staging] for project demo-shop.
  hint: Add "qa" to envs.available in sdods.project.yaml and create envs/qa.yaml.
  docs: https://docs.sdods.com/docs/guides/configuration

3 answers

• 31votes✓

  Accepted answer

  Because the declaration is the list, and the file is the detail. envs.available is what project list, the CI matrix and the web UI enumerate; a stray file in envs/ is not an environment until the project says it is.

  yamlCopy

  envs:
    default: staging
    available: [local, staging, qa]

  The order matters for the error you get next: availability is checked first, file existence second. So if you had done it the other way round — declared qa with no file — you would have seen

  textCopy

  ✖ ENV_NOT_FOUND: Environment "qa" has no file at /work/shop-tests/projects/demo-shop/envs/qa.yaml

  Two errors, two different halves of the same mistake.

  RNanswered by Reeta Nandalmaintainer41,280 · 11 May 2021
• 14votes

  There is a command that does both halves and keeps the comments in your project yaml intact:

  bashCopy

  sdods env add qa -p demo-shop --ui-url https://qa.example.com --api-url https://api-qa.example.com

  It writes envs/qa.yaml and appends qa to envs.available. Add --default if it should become the default environment.

  DOanswered by Daniel Oyelaranmaintainer24,177 · 12 May 2021
• 5votes

  Also worth knowing that -e is not the only way in. The environment is picked in this order: the -e flag, then whatever the caller passed programmatically, then SDODS_ENV, then envs.default from the project file. A leftover SDODS_ENV=qa in a shell profile produces exactly this error with no -e in sight.

  RGanswered by Rafa Garrido12,996 · 20 May 2021