Struct StatusResponse 

#[non_exhaustive]
pub struct StatusResponse {
    pub backup_now: Vec<String>,
    pub check_severities: HashMap<String, CheckSeverity>,
    pub tags: TagMap,
}

The status-push response: only the return-path instructions the device can act on. The stored status record is deliberately not echoed back — the device already has everything it sent.

JSON schema

{
 "description": "The status-push response: only the return-path instructions the device\ncan act on. The stored status record is deliberately not echoed back —\nthe device already has everything it sent.",
 "type": "object",
 "required": [
   "backup_now",
   "check_severities",
   "tags"
 ],
 "properties": {
   "backup_now": {
     "description": "Backup types the server should back up now: operator-requested\none-offs plus scheduled backups that are due. Each serializes as a\nplain string (e.g. `\"tamanu-postgres\"`). The device should run each\nlisted type, then report via `POST /backup-report`; an empty list\nmeans nothing to do. Only sent to `alertd` pushes (the agent that\nruns backups); other sources always receive an empty list.",
     "type": "array",
     "items": {
       "type": "string"
     }
   },
   "check_severities": {
     "description": "The effective handling of every healthcheck canopy knows about, keyed\nby check name (as reported in `health[].check`): `skip` (silenced for\nthis server, or classified below warning), `warn` (warning), or `fail`\n(error or critical). Only the static severity baseline is reflected —\noperator-defined conditional rules are evaluated per push and not\nincluded. Checks absent from the map are new to canopy and default to\n`warn`. Clients that predate this field can safely ignore it; the\nsame mapping is served on demand at `GET /status/{server_id}/check-severities`.",
     "type": "object",
     "additionalProperties": {
       "$ref": "#/components/schemas/CheckSeverity"
     },
     "propertyNames": {
       "type": "string"
     }
   },
   "tags": {
     "description": "The server's effective tags: its own tags overlaid on its group's,\nplus the synthetic read-only `canopy:` tags and effective `billing.*`\nlabels. Identical to what the standalone `GET /tags` endpoint\nreturns — see that endpoint for the full contract. Clients that\npredate this field can safely ignore it.",
     "$ref": "#/components/schemas/TagMap"
   }
 }
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

backup_now: Vec<String>

Backup types the server should back up now: operator-requested one-offs plus scheduled backups that are due. Each serializes as a plain string (e.g. "tamanu-postgres"). The device should run each listed type, then report via POST /backup-report; an empty list means nothing to do. Only sent to alertd pushes (the agent that runs backups); other sources always receive an empty list.

check_severities: HashMap<String, CheckSeverity>

The effective handling of every healthcheck canopy knows about, keyed by check name (as reported in health[].check): skip (silenced for this server, or classified below warning), warn (warning), or fail (error or critical). Only the static severity baseline is reflected — operator-defined conditional rules are evaluated per push and not included. Checks absent from the map are new to canopy and default to warn. Clients that predate this field can safely ignore it; the same mapping is served on demand at GET /status/{server_id}/check-severities.

tags: TagMap

The server’s effective tags: its own tags overlaid on its group’s, plus the synthetic read-only canopy: tags and effective billing.* labels. Identical to what the standalone GET /tags endpoint returns — see that endpoint for the full contract. Clients that predate this field can safely ignore it.

Implementations

impl StatusResponse

pub fn builder() -> StatusResponseBuilder

Create an instance of StatusResponse using the builder syntax

Trait Implementations

impl Clone for StatusResponse

fn clone(&self) -> StatusResponse

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for StatusResponse

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for StatusResponse

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for StatusResponse

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.