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.
We have three environments that serve identical payloads. Re-recording the same traffic three times feels silly. sdods har list prints an env column so I assume the answer is no, but before I go symlinking directories: is the environment part of the lookup, or just part of the display?
bun run sdods har list -p demo-shopAccepted answer
It is part of the path, so it is part of the lookup. Files live at:
projects/<slug>/har/<env>/<name>.har
projects/<slug>/har/<env>/<name>.har.jsonThe directory comes from the resolved environment name, so a scenario running with -e staging can only ever see har/staging/. There is no fallback to another env and no way to point one env at another file.
The tag names the file, the environment names the directory. So @har:products is one tag that maps to a different recording per env, which is usually what you want anyway: the hosts in the recorded URLs differ per environment, and a staging HAR replayed against prod URLs would miss on every entry.
Do not symlink. The sidecar records which project and env it was captured against, and the first time the payloads diverge you will spend an afternoon working out why one env is asserting on the other one’s data.
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.