salmon-article-93420
05/14/2024, 2:36 PMmicroscopic-river-74022
05/14/2024, 2:36 PMmicroscopic-river-74022
05/14/2024, 2:36 PMtimeout configuration key in your Garden configuration file. The timeout key specifies the maximum time in seconds that Garden should wait for a command to finish.
The timeout key can be set in different contexts depending on the type of operation you want to adjust the timeout for:
- For the build process, you can set the timeout key under the build configuration. For example, in the exec, container, templated, hadolint, and conftest module types. The default value is 600 seconds. source 1 (), source 3 (), source 5 (), source 9 (), source 11 ()
- For task execution, you can set the timeout key under the tasks configuration. For example, in the exec, helm, and container module types. The default value is 600 seconds. source 2 (), source 8 (), source 10 ()
- For services, you can set the timeout key under the services configuration in the exec module type. The default value is 600 seconds. source 4 ()microscopic-river-74022
05/14/2024, 2:36 PMstatusCommand in the syncMode of services in the exec module type, you can set the timeout key. The default value is 10 seconds. source 6 ()
Here is an example of how to set the timeout key in the build configuration:
yaml
kind: Module
type: exec
name: my-module
build:
timeout: 1200 # Increase the timeout to 1200 seconds
Please replace my-module with the actual name of your module and exec with the actual type of your module. The timeout value should be replaced with the desired timeout in seconds.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------microscopic-river-74022
05/14/2024, 2:36 PM