diff options
| author | Jae Hoon Kim <kimjae@chromium.org> | 2019-09-03 12:56:32 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-09-27 18:30:08 -0700 |
| commit | 051627abe8995741f996e3931d899c0b08e503eb (patch) | |
| tree | 170f7e778cff0daeb5a9aa8d8b1d9b7354097828 /scripts/update_payload/applier.py | |
| parent | f407f187af489b92c9a50a1f4ac8cf703b8fab56 (diff) | |
update_engine: Parse and supply EOL date for Chrome
From Omaha, the optional field |_eol_date| is to indicate the EOL of a
device. Chrome side will leverage these values to display a
notification. The value for |_eol_date| should be an integer value
indicating the days from Unix Epoch date.
If |_eol_date| does not exist in the Omaha response or have non-integer
values, the default will fallback to |kEolDateInvalid|.
BUG=chromium:998983
TEST=FEATURES="test" emerge-$B update_engine update_engine-client system_api
TEST=test_that -b $B $IP autoupdate_EOL
TEST=test_that -b $B $IP autoupdate_EOL.approaching_eol
TEST=test_that -b $B $IP autoupdate_EOL.future_eol
Cq-Depend:chromium:1783596, chromium:1811116
Change-Id: I2b1063873118ccf8fe22ba09a5961e27aa980c7b
Reviewed-on: https://chromium-review.googlesource.com/1783897
Tested-by: Jae Hoon Kim <kimjae@chromium.org>
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
Diffstat (limited to 'scripts/update_payload/applier.py')
0 files changed, 0 insertions, 0 deletions