Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-979

Preconditions for disrupting device



    • Type: Epic
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Epic Name:
      Preconditions for disrupting device
    • Epic Total Estimate:
    • DoD:
      show more show less


      Many consumer devices, especially those with a display require user acknowledgement or control before disrupting the device (e.g. rebooting or using a lot of resources during installation).
      This is most typically done by showing a UI pop-up before rebooting the device, asking if an update should be applied. Typically a Changelog is included here as well; what extra value will the user get after the update - this is obviously different for each update.

      However, there could be many ways to notify the user and ask for "permission" so this needs to be modular.

      More generically, there might be other types of conditions, like the if device has been idle for 15 minutes (by some measurement - e.g. user has not touched it or the sun is not shining), has enough battery left, and/or the local time is 3am-5am. So it needs to be modular in terms of the check policy as well.

      Acceptance criteria

      • It is possible for users to implement a user confirmation at the device and the device will only be rebooted after confirmation
      • It is possible for users to show a custom message while device is being disrupted (e.g. rebooted)
      • There is a modular way for users to define preconditions before a device is disrupted


          Issue Links



              • Assignee:
                a10003 Eystein Maloy Stenberg
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:

                  Summary Panel