API behaviour change more info needed

[Manxmann]

Hi Folks,

I just upgraded a couple of my firewalls to test the new 25.x release stream before committing to move our entire estate.

So far everything looks good and we've only encountered one niggle, specifically the API responses seems to have changed e.g.

On a 24.x series and earlier instance calling core/system/status would return:

{
  "CrashReporter": {
    "statusCode": 2,
    "message": "No problems were detected.",
    "logLocation": "/crash_reporter.php",
    "timestamp": "0",
    "status": "OK"
  },
  "Firewall": {
    "statusCode": 2,
    "message": "No problems were detected.",
    "logLocation": "/ui/diagnostics/log/core/firewall",
    "timestamp": "0",
    "status": "OK"
  },
  "System": {
    "status": "OK"
  }
}

Since the 25.x upgrade this same call now returns:

{
  "metadata": {
    "system": {
      "status": 2,
      "message": "No pending messages",
      "title": "System"
    },
    "translations": {
      "dialogTitle": "System Status",
      "dialogCloseButton": "Close"
    },
    "subsystems": []
  }
}


It appears that the 3 previous sections, crash reporter / firewall / system, have been combined into a single 'No pending messages' response.

No problem and this kinda makes sense, the issue is I can't find documentation on what the various responses will be in the event of say a PHP crash or a firmware update failure, thus we cannot code around that change.

Can anyone provide me with info or a link to the 'Status/Message' responses that may be returned?

Cheers :)