Proposal
Larger containers like elasticsearch, cosmos etc. routinely time out for me. When using custom setups that's fine, however this is an issue when using modules as I cannot set the startup timeout.
It would be great if there was a way to override the default startup timeout globally through an env var or even disable it entirely and rely solely on the context for timeout.
In a perfect world I think it should not even exist at all and the context should be used to control it as mentioned in #3065 but having a simple env var would be a cheap way to fix this with a very small blast radius.
I'm happy to contribute a PR if you guys would be open to this.
Proposal
Larger containers like elasticsearch, cosmos etc. routinely time out for me. When using custom setups that's fine, however this is an issue when using modules as I cannot set the startup timeout.
It would be great if there was a way to override the default startup timeout globally through an env var or even disable it entirely and rely solely on the context for timeout.
In a perfect world I think it should not even exist at all and the context should be used to control it as mentioned in #3065 but having a simple env var would be a cheap way to fix this with a very small blast radius.
I'm happy to contribute a PR if you guys would be open to this.