hawkBit has support for specifying when an update should be applied and when it should not, a feature named "maintenance window".
See the commit message for details on how the feature is implemented in hawkBit:
eclipse-hawkbit/hawkbit@f4278c4
The maintenance window feature is supposed to work both on soft and forced updates.
Here's an excerpt of the deployment base JSON with a forced update:
{
"id": "6",
"deployment": {
"download": "forced",
"update": "forced",
...
}
}Here's an excerpt of the deployment base JSON with a forced update with a closed maintenance window:
{
"id": "7",
"deployment": {
"download": "forced",
"update": "skip",
"maintenanceWindow": "unavailable",
...
}
}Here's an excerpt of the deployment base JSON with a forced update with an open maintenance window:
{
"id": "7",
"deployment": {
"download": "forced",
"update": "forced",
"maintenanceWindow": "available",
...
}
}
hawkBit has support for specifying when an update should be applied and when it should not, a feature named "maintenance window".
See the commit message for details on how the feature is implemented in hawkBit:
eclipse-hawkbit/hawkbit@f4278c4
The maintenance window feature is supposed to work both on soft and forced updates.
Here's an excerpt of the deployment base JSON with a forced update:
{ "id": "6", "deployment": { "download": "forced", "update": "forced", ... } }Here's an excerpt of the deployment base JSON with a forced update with a closed maintenance window:
{ "id": "7", "deployment": { "download": "forced", "update": "skip", "maintenanceWindow": "unavailable", ... } }Here's an excerpt of the deployment base JSON with a forced update with an open maintenance window:
{ "id": "7", "deployment": { "download": "forced", "update": "forced", "maintenanceWindow": "available", ... } }