NetworkMachineManageResult network.machine-manage-result@1

Generated at 2026-11-13 06:25:48 UTC from openvibe-contracts v0.419.0 and openvibe-sdk v0.161.0.

Version

1.0.0

Owner

network

Visibility

first-party

Status

active

Compatibility

backward

Schema

https://openvibe.network/contracts/network/machine-manage-result.v1.json

network.machine-manage-result@1: the machine as it is after a change (plan L34, step M2: PATCH /api/v1/machines/:id, PUT /api/v1/machines/:id/roles, POST /api/v1/machines/:id/revoke). The pairing route answers network.machine-pairing@1 instead, because a pairing is a code and not a machine.

Fields

Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

{
  "machine": {
    "id": "dev_01JAB2C3D4E5F6G7H8J9K0MNPS",
    "name": "Kitchen server",
    "kind": "server",
    "os": "linux",
    "online": true,
    "last_seen_at": "2026-10-31T09:00:00.000Z",
    "node_version": "0.15.0",
    "roles": [
      "codes.worker"
    ],
    "running": [
      {
        "kind": "codes.jobs",
        "count": 1
      }
    ]
  }
}

{
  "machine": {
    "id": "x",
    "kind": "server",
    "online": false,
    "roles": [],
    "running": []
  }
}

{}

Validate

const contracts = require('openvibe-contracts');
contracts.validate('network.machine-manage-result@1', value);   // { valid, errors: [{ path, message }] }