Currently, the self-update endpoint is used by IncusOS only in a very limited number of cases (initial registration, network config change, provider change). In order to keep Operations Center's state better in sync with the actual state of the managed servers, this mechanism should be extended to also support other cases, where updating Operations Center's state is favorable.
For this, the request body sent with a self update request (https://github.com/FuturFusion/operations-center/blob/main/shared/api/provisioning_server.go#L826-L830) is extended with the cause for the self update request.
Possible causes for a self update request are:
- System is ready (system is back online, e.g. after a reboot or when newly started)
- OS update applied
- Application update applied
- Network config changed (current)
- Network interface state changed (e.g. management network interface is back online)
- Storage config changed
- System is reboot triggered
- System is shutdown triggered
Relates to: #801
Currently, the self-update endpoint is used by IncusOS only in a very limited number of cases (initial registration, network config change, provider change). In order to keep Operations Center's state better in sync with the actual state of the managed servers, this mechanism should be extended to also support other cases, where updating Operations Center's state is favorable.
For this, the request body sent with a self update request (https://github.com/FuturFusion/operations-center/blob/main/shared/api/provisioning_server.go#L826-L830) is extended with the cause for the self update request.
Possible causes for a self update request are:
Relates to: #801