Restart safety: transient credential checks are 1013/503, not a refusal
- A device credential that cannot be checked now (device store not running, nonces unreadable) raises DeviceUnavailable: 503 over HTTP, and the /flows/ws handshake and the tunnel stream accept and close with 1013. 1008 (a 403 before accepting) stays for a revoked or invalid one - Device files are written through a temporary file, so a read mid-save no longer looks like a deleted device - The first report turns Touch friendly on only for a device paired since pairings are noted (DeviceState.paired_at), so devices paired before keep the switch they were given - NodeDef reads `device`/`device_policy` from older clients as the worker label, for a release - Tests: transient vs revoked socket, the touch default, the old worker keys, and a restart with a device node and a node_health rule sending no push
This commit is contained in:
@@ -226,6 +226,27 @@ class NodeDef(BaseModel):
|
||||
),
|
||||
)
|
||||
|
||||
@model_validator(mode="before")
|
||||
@classmethod
|
||||
def _old_worker_keys(cls, data: Any) -> Any:
|
||||
"""Read ``device`` and ``device_policy`` as the worker label they were.
|
||||
|
||||
What a ``fluksio sync`` or SDK from before the rename to ``worker``
|
||||
sends, which would otherwise be dropped without a word. A new key
|
||||
sent beside an old one wins.
|
||||
|
||||
ponytail: drop after a release, once clients have caught up.
|
||||
"""
|
||||
if not isinstance(data, dict) or not (
|
||||
"device" in data or "device_policy" in data
|
||||
):
|
||||
return data
|
||||
data = dict(data)
|
||||
for old, new in (("device", "worker"), ("device_policy", "worker_policy")):
|
||||
if old in data:
|
||||
data.setdefault(new, data.pop(old))
|
||||
return data
|
||||
|
||||
@field_validator("id")
|
||||
@classmethod
|
||||
def _check_id(cls, value: str) -> str:
|
||||
|
||||
Reference in New Issue
Block a user