Put workspace: payments in a new project so it would not sit with the rest. Now every command in the repo fails, including ones about other projects:
✖ CONFIG_INVALID: Project "billing" references workspace "payments" which is not declared in sdods.workspace.yaml.
hint: Declared workspaces: default, platform-qa. Add it to workspaces[] or fix the project's workspace: field.Why does one project break sdods project list for all of them?
Accepted answer
Because discovery is eager: every project under projects/ is parsed and checked on startup, before any command decides which project it cares about. A repo where one project is misfiled is a repo with a broken hierarchy, and finding that out only when you happen to name that project would be worse.
Declare it and everything comes back:
workspaces:
- { slug: default, name: Default workspace, organization: sdods }
- { slug: platform-qa, name: Platform QA, organization: sdods }
- { slug: payments, name: Payments, organization: sdods }
defaultWorkspace: defaultThere are two siblings of this error you will meet eventually:
✖ CONFIG_INVALID: Project "billing" references organization "acme" but this repo belongs to "sdods".
✖ CONFIG_INVALID: defaultWorkspace "payments" is not declared in workspaces[] of /work/shop-tests/sdods.workspace.yaml.One repo is one organization; workspaces are how you split teams inside it.
Omitting workspace: entirely is also legal — the project then joins defaultWorkspace. We only set it explicitly on the projects that genuinely belong elsewhere, which keeps the diff small when the workspace list changes.
To see the result rather than guess at it:
sdods workspace treeOrganization, then workspaces, then the projects in each with their modules and processes. It is the quickest check that a project landed where you meant it to.
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a question