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.
Hand-edited an environment file and got a list back instead of one message:
✖ CONFIG_INVALID: Invalid configuration in /work/shop-tests/projects/demo-shop/envs/staging.yaml:
• ui.baseUrl: Invalid URL
• api.baseUrl: Invalid input: expected string, received undefined
docs: https://docs.sdods.com/docs/guides/configurationThe api.baseUrl one confuses me most — it is definitely in the file.
Accepted answer
Each bullet is one schema issue: the dotted path inside the file, then the reason. Both of yours are real.
ui.baseUrl needs a scheme. www.saucedemo.com is not a URL; https://www.saucedemo.com is.
api.baseUrl reporting as missing almost always means the indentation put it somewhere else — under ui, or at the top level — so the api block genuinely has no baseUrl. Check the column of the key, not its spelling:
ui:
baseUrl: https://www.saucedemo.com
api:
baseUrl: https://jsonplaceholder.typicode.com
headers: { Accept: application/json }The paths are relative to the file, so ui.baseUrl here, not env.ui.baseUrl. The env. prefix only appears once the file has become part of the resolved tree — that is why unresolved-variable errors carry it and schema errors do not.
Run it as a pre-push hook and you never see this on a build agent:
sdods config validateIt resolves every project against every environment it declares and stops at the first failure, exit 2.
Both the project file and the environment file go through the same reporting, so the same bullet format shows up for sdods.project.yaml too. The file path on the first line is the only thing that tells you which one you broke — worth reading before you go editing the wrong file, which I have now done twice.
Have a different question? Ask it.