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.
sdods run -p demo-shop -e staging -m api✖ CONFIG_INVALID: Unknown module "api" for project demo-shop.
hint: Known modules: auth, inventory, cart, posts-api, hybrid.The directory is features/api/, so where does posts-api come from? -m cart works and that folder is features/cart/.
Accepted answer
-m takes the module name, not the folder. They are usually the same because path defaults to the name, but they do not have to be:
modules:
- name: posts-api
title: Posts API
path: api
layers: [api]So cart works because that module never set path, and api fails because it is a folder, not a module.
sdods run -p demo-shop -e staging -m posts-apiThe hint always lists the real names, which is the fastest way to check without opening the yaml.
The names are also what the module carries elsewhere — its testing types, the tag every scenario in it should have, its owner and Jira component. Keeping name readable and letting path be whatever the folder is called historically is fine; we did the reverse for a while and ended up with a module called svc-2.
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.