You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the /mode resource traverses the symbolic links and returns the target indicated by the link. This, however, isn't necessarily what is running. If an update was made, it will only take effect after reboot.
Return what the target that is actually running.
Should we return both a current and next state?
The text was updated successfully, but these errors were encountered:
The complexity of managing "running" mode vs "next" mode has me leaning back towards the original approach: automatically apply the router card mode when changing it. For now, that means rebooting. GETs should return the actually running mode, not the default symlink.
Eventually just systemctl isolate <new-target> might suffice --- but will require more extensive testing.
The alternative is to specify a generic approach for defining "running" config vs "next" config and promoting "next" to "running". Presumably a reboot (whether intentional or not) would do this for all types of config. For some types, those a simpler action might suffice. Sending SIGHUP to connman for wifi config or systemctl isolate new-target for mode.
Possible strawmen are
{ "config" : {
"active" : {
"wifi" : ...,
"mode" : ...
},
"pending" : {
"wifi" : ..., # objects not pending would be omitted
"mode" : ... # pending would be the empty object if no changes were pending
}
"serial_number" : ...,
"control_address" : ...,
"mac_address" : {... },
...,
"status" : {
"wifi" : {
"enabled" : true,
"IPv4_address" : ...,
...
}
}
}
Currently, the /mode resource traverses the symbolic links and returns the target indicated by the link. This, however, isn't necessarily what is running. If an update was made, it will only take effect after reboot.
Return what the target that is actually running.
Should we return both a current and next state?
The text was updated successfully, but these errors were encountered: