There is no way to define such timeout on the one-off counterparts request and exec, letting us being on the mercy of the HTTP client timeout, that is not documented in Kurtosis Docs.
Desired behaviour
request and exec should have sane, documented timeout defaults and make it customizable. Ideally timeout could be part of recipe instead of being binded by the recipe executor
How important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.
Background & motivation
Currently
wait
has atimeout
field to indicate the maximum time a single call ofrecipe
should take, before moving on to the next call: https://docs.kurtosis.com/starlark-reference/plan/#waitThere is no way to define such
timeout
on the one-off counterpartsrequest
andexec
, letting us being on the mercy of the HTTP client timeout, that is not documented in Kurtosis Docs.Desired behaviour
request
andexec
should have sane, documented timeout defaults and make it customizable. Ideally timeout could be part of recipe instead of being binded by the recipe executorHow important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.