Support changing from non-canary to canary channel in update engine.
Now that we have added support in lsb-release for both the board appid
and canary app id to be specified, we should use the appropriate appid
according to the channel from which we want to download the new payload.
This change in update engine will enable the change from non-canary to
canary channels. This feature when be lit up end to end when the UI for
this scenario is ready.
BUG=chromium:225866
TEST=Unit tests pass. Tested all channel changes on my ZGB.
Change-Id: Ia9c37c72f53f6c69436f0a96e35d2584d84653c8
Reviewed-on: https://gerrit.chromium.org/gerrit/47181
Commit-Queue: Jay Srinivasan <jaysri@chromium.org>
Reviewed-by: Jay Srinivasan <jaysri@chromium.org>
Tested-by: Jay Srinivasan <jaysri@chromium.org>
diff --git a/omaha_request_action.cc b/omaha_request_action.cc
index 6391208..ad1f95e 100644
--- a/omaha_request_action.cc
+++ b/omaha_request_action.cc
@@ -200,13 +200,8 @@
string delta_okay_str = params->delta_okay() ? "true" : "false";
- // Use the default app_id only if we're asking for an update on the
- // canary-channel. Otherwise, use the board's app_id.
- string request_app_id =
- (download_channel == "canary-channel" ?
- params->app_id() : params->board_app_id());
string app_xml =
- " <app appid=\"" + XmlEncode(request_app_id) + "\" " +
+ " <app appid=\"" + XmlEncode(params->GetAppId()) + "\" " +
app_versions +
app_channels +
"lang=\"" + XmlEncode(params->app_lang()) + "\" " +