Micro updates are application updates. You can update your application's code, install new packages, and run bash commands before/after the update is deployed. Usually, you would use a Micro update to deploy a new release of your application or patch a bug on your entire fleet of devices.
Creating and deploying a Micro update is easy and takes just a few moments. There is a recipe to fill which consists of multiple stages:
1. General details - overall information regarding the update. Things like the update version, which devices to deploy the update on, a comment for later reference, etc.
2. Before update - whether to run a Bash command/script before the update or not. If yes, enter the bash command/script to run.
3. Upload files/directories - choose files/directories to upload to the devices during the update.
4. Install dependencies - choose packages to install on the devices. Currently supported package managers:
5. After update - whether to run a Bash command/script after the update or not. If yes, enter the bash command/script to run.
6. Rollback - choose what to do in case the update fails to deploy. Things like revert to the previous files/directories, execute a Bash command, reboot the device, etc..
That's it. Clicking on the
Deploybutton will begin the deployment on the devices you have selected.
Tip - Before deploying a Micro update on a Production group, it is recommended to deploy the Micro update on a Test group first and make sure that everything works as planned.
When the update's status turns to Success, go back to the
Updatescategory, to the recent updates table, find the relevant Micro update row and click on
Deploy to othersin order to deploy the same Micro update on another group.
You can choose to run a Bash command or a Bash script before and/or after the Micro update is deployed on the edge device.
It is recommended to use the 'Before' and 'After' commands to stop and start the device application service.
Any command that is requiring user input. If such a command is run, the update will stuck. The solution for that can be to run the next command before your command:
DEBIAN_FRONTEND=noninteractive. In any case, it is recommended to check that this solution works with your devices.
When creating a new Micro update, make sure to fill the
Micro Update Rollbacksection as desired. Those settings will be executed when a Micro update fails for any reason.
After deploying a Micro update on your device fleet, up until the deployment is finished, you have the option to Abort the update.
Aborting an update is not recommended in any case. You should abort the update only in emergency cases OR if the update didn't start the deployment yet. The Abort command will be sent to the device on the next Device communication cycle. So keep in mind that some time may pass between your click on the
Abortbutton and the actual abort.
To abort an update, go to the
Recent updatestable, click on the
Update detailscolumn, and then on the
The abort option available for Connect Agent versions