Allow bypassing handler spawning logic #755
Hey, it'd be super sweet if there was a native solution for #748. Maybe
The text was updated successfully, but these errors were encountered:
We did some work around how Dredd is friendly to the Docker setup, but this hasn't been resolved yet. It needs internal refactoring of how the hooks are done in Dredd. The discussion in #748 completely describes the original problem this is trying to solve.
This is also related to #1101 - when re-thinking the
When using Dredd with non-JS hooks, Dredd needs a hooks handler process. By default, Dredd spawns it as a subprocess and connects to it on a default port over TCP, then Dredd does its job and then kills the hooks handler process before the end of the testing.
When used with Docker, people want to run the hooks handler process in a separate container. Dredd supports an option for specifying a non-default port, that's OK, but it requires a
It's possible to call Dredd with
This issue can be closed if Dredd provides a way to opt-out from spawning the hooks handler process.