Skip to content

← All questions

SDODS_UI_BASE_URL in the build image overrides -e staging and there seems to be no flag to beat it

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

Our agent image exports SDODS_UI_BASE_URL=http://localhost:3000 for an unrelated tool. Runs pick the staging environment correctly — the API side goes to the staging API — but every browser lands on localhost.

bash
sdods run -p demo-shop -e staging -l ui -b chromium -t @smoke
sdods config show -p demo-shop -e staging --explain
text
env.ui.baseUrl   processEnv  http://localhost:3000
env.api.baseUrl  envYaml     https://jsonplaceholder.typicode.com

So I understand what is happening — the mapped variable writes the path directly and sits above the env file. What I cannot work out is whether -e is meant to win here, since selecting an environment and then not using its base URL feels like it defeats the point. And run does not seem to take a --ui-base-url to override it back from layer 6.

Is unsetting the variable the only route, or is there something on the run command I have missed?

configci
asked by Devon Marsh

No answers yet

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

Related