diff options
author | Roman Melnikov | 2023-11-01 12:42:30 +0100 |
---|---|---|
committer | Roman Melnikov | 2023-11-02 11:29:52 +0100 |
commit | aeeee3c1e3e9bfc38462cb315b6e19ee9fe6db70 (patch) | |
tree | db04d30c6df0f6f19ccdfc6070da00c5bbf4d1b8 /src/lib.rs | |
parent | d50737080327575d78fe7490b20fcc3eba9f1d72 (diff) |
[Chore] Make activation wait timeout configurable
Problem: Currently profile activation waiting timeout is hardcoded to
240 seconds, see https://github.com/serokell/deploy-rs/pull/48.
In some cases, this timeout can be exceeded (e.g.
activation performs a heavy DB migration and waits for it to finish
before considering the profile activation succesful).
Solution: Make this timeout configurable via 'activationTimeout' deploy
attribute or corresponding '--activation-timeout' CLI option. For the
sake of backward compatibility, the new 'wait' subcommand
'--activation-timeout' option is made optional and defaults to 240
seconds if it wasn't provided.
Diffstat (limited to 'src/lib.rs')
-rw-r--r-- | src/lib.rs | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -163,6 +163,7 @@ pub struct CmdOverrides { pub magic_rollback: Option<bool>, pub temp_path: Option<PathBuf>, pub confirm_timeout: Option<u16>, + pub activation_timeout: Option<u16>, pub sudo: Option<String>, pub dry_activate: bool, pub remote_build: bool, @@ -444,6 +445,9 @@ pub fn make_deploy_data<'a, 's>( if let Some(confirm_timeout) = cmd_overrides.confirm_timeout { merged_settings.confirm_timeout = Some(confirm_timeout); } + if let Some(activation_timeout) = cmd_overrides.activation_timeout { + merged_settings.confirm_timeout = Some(activation_timeout); + } DeployData { node_name, |