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.
Added a use: block to the staging file and now nothing runs:
✖ CONFIG_INVALID: Cannot parse YAML at /work/shop-tests/projects/demo-shop/envs/staging.yaml: All mapping items must start at the same column at line 12, column 3
docs: https://docs.sdods.com/docs/guides/configurationLine 12 looks identical to line 11 to me.
Accepted answer
It will be a tab. Tabs are never valid indentation in YAML, and they line up perfectly in an editor that renders them as spaces.
That message is the YAML parser talking, not SDODS — the file never gets as far as the schema, which is why you see a parse error rather than a list of field problems. Line and column are the parser's, so they point at the real character.
Set your editor to insert spaces for .yaml, and check the whole tree in one shot before pushing:
sdods config validateThe other reliable producer of that exact message is a two-space indent under a key that already opened a flow mapping on the same line, e.g.
use: { locale: en-US }
timezoneId: America/New_YorkPick one style per block — either all flow or all block — and it goes away.
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.