update_engine: Populate UpdateCheckParams with rollback policies.
These are the policies introduced in crrev.com/c/916563,
controlling what should happen if target_version_prefix is
earlier than the current Chrome OS version, and how long Chrome
OS rollback protection should be postponed.
BUG=chromium:813036
TEST='cros_run_unit_tests --board=cyan --packages update_engine'
Change-Id: I33cf3b8975b52ca4b647a4b69a2d7879a9115d3c
Reviewed-on: https://chromium-review.googlesource.com/929321
Commit-Ready: Marton Hunyady <hunyadym@chromium.org>
Tested-by: Marton Hunyady <hunyadym@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
diff --git a/update_manager/default_policy.cc b/update_manager/default_policy.cc
index 5da1520..0cd58fb 100644
--- a/update_manager/default_policy.cc
+++ b/update_manager/default_policy.cc
@@ -40,6 +40,8 @@
result->updates_enabled = true;
result->target_channel.clear();
result->target_version_prefix.clear();
+ result->rollback_to_target_version = RollbackToTargetVersion::kUnspecified;
+ result->rollback_allowed_milestones = -1; // No version rolls should happen.
result->is_interactive = false;
// Ensure that the minimum interval is set. If there's no clock, this defaults