You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Add the function of validate_expected_version that would check that we have the flag of expected_version and it is from the supported versions we allow. Also, add specific errors to the CLI (MissingExpectedVersionFlag and InvalidArgumentType) so that eventually we would not report it as UpgradeFailed.
2. Move functions that are related to versions to versions_utils, and added a helper function is_valid_sematic_version to check the structure of the string.
3. Throw an error instead of the message "config_dir_version on system.json and config_fs.config_dir_version match, nothing to upgrade" and change the tests accordingly.
4. Add the skip_verification to BOOLEAN_STRING_OPTIONS and use it to in validate_expected_version.
Signed-off-by: shirady <[email protected]>
expect(parsed_res.error.cause).toContain(`config dir upgrade can not be started - the host's package version=${pkg.version} does not match the user's expected version=${expected_version}`);
340
+
expect(parsed_res.error.cause).toContain(`expected_version must match the package version`);
310
341
});
311
342
312
343
it('upgrade start - should fail on old rpm version',async()=>{
if(!should_upgrade(config_dir_from_version,config_dir_to_version))return{message: 'config_dir_version on system.json and config_fs.config_dir_version match, nothing to upgrade'};
0 commit comments