Endpoint

/v1/frozen/bridges/{filesystem_uuid}

GET

Returns the bridge. Returns HTTP 404 if no Frozen bridge has this UUID.

Parameters

Name Description Required
filesystem_uuid The Frozen bridge's filesystem UUID, as `GET /v1/frozen/bridges/` reports it. Yes

Response

Codes

Code Description
200 Return value on success

Schema

{
  "description": "api_frozen_bridge",
  "type": "object",
  "properties": {
    "filesystem_uuid": {
      "description": "The bridge's filesystem UUID.",
      "type": "string"
    },
    "mount_path": {
      "description": "Absolute path of the bridge's directory on the cluster, without a trailing slash.",
      "type": "string"
    },
    "allow_archived_metadata_changes": {
      "description": "Whether clients can change the metadata and named streams of a file that is frozen, offline or restoring; see the create request's field.",
      "type": "boolean"
    }
  }
}

DELETE

Deletes the bridge, which must be empty. To delete a bridge's files and their data, delete its top-level files and folders with a Frozen delete first, and wait for the cluster to finish deleting them. File access across the cluster pauses briefly during this call while the cluster restarts its services, so delete a bridge while clients are quiet. Returns HTTP 409 if the bridge holds any file or folder, while a job on the bridge is still running or stopping, or while the cluster is still deleting files deleted from the bridge, such as one a client holds open, or still deleting their data, which usually takes up to a few hours; and HTTP 404 if no Frozen bridge has this UUID. If the cluster is still deleting files after a day, contact Qumulo.

Parameters

Name Description Required
filesystem_uuid The Frozen bridge's filesystem UUID, as `GET /v1/frozen/bridges/` reports it. Yes

Response

Codes

Code Description
204 Return value on success