chromium/components/policy/resources/templates/policy_definitions/DeviceUpdate/DeviceUpdateStagingSchedule.yaml

caption: The staging schedule for applying a new update
desc: |-
  This policy defines a list of percentages that will define the fraction of <ph name="PRODUCT_OS_NAME">$2<ex>Google ChromeOS</ex></ph> devices in the OU to update per day starting from the day the update is first discovered. The discovery time is later than the update published time, since it could be a while after the update publishing until the device checks for updates.

        Each (day, percentage) pair contains which percentage of the fleet has to be updated by the given number of days since the update has been discovered. For example, if we have the pairs [(4, 40), (10, 70), (15, 100)], then 40% of the fleet should have been updated 4 days after seeing the update. 70% should be updated after 10 days, and so on.

        If there is a value defined for this policy, updates will ignore the <ph name="DEVICE_UPDATE_SCATTER_FACTOR_POLICY_NAME">DeviceUpdateScatterFactor</ph> policy and follow this policy instead.

        If this list is empty, there will be no staging and updates will be applied according to other device policies.

        This policy does not apply for channel switches.
device_only: true
example_value:
- days: 7
  percentage: 50
- days: 10
  percentage: 100
features:
  dynamic_refresh: true
owners:
- [email protected]
- [email protected]
- [email protected]
schema:
  items:
    $ref: DayPercentagePair
    description: Contains the number of days and the percentage of the fleet that
      should be updated after those days have passed.
  type: array
supported_on:
- chrome_os:69-
tags:
- system-security
type: dict
generate_device_proto: False