Abort multipart upload

Outcome

Ask R2 to abandon an existing multipart upload using its scoped key and uploadId; completed objects are separate from unfinished parts.

Before you start

• Verify identity, pin environment and organization, and discover a granted Bytes workspace before choosing file keys.
• The action requires files:write. Select a verified workspace resource separately from action input; a body field cannot supply a workspace grant.
• Scope org uses the verified workspace shared root; private uses the caller’s private subtree. The accepted legacy all value resolves to org and does not grant cross-organization browsing. The bucket input cannot switch the configured R2 binding.
• Authorize the described effect or private-data export before passing CLI --confirm or MCP confirm:true. GET listing/search can persist derived data; HTTP method alone does not establish a read-only action.

Discover the target

topolo whoami --json
topolo actions get app_topolo_bytes.uploads.multipart.abort --detail --json
topolo resources topolo-bytes --json
topolo workspaces list topolo-bytes --json
topolo actions get app_topolo_bytes.uploads.multipart.create --detail --json

• File keys are paths returned by files.list/search in the selected workspace and scope. Discover the granted workspace id; do not derive access from fixture ids.
• Reuse both key and uploadId from multipart.create; preserve each uploaded partNumber and ETag for completion.

Request

POST /api/multipart/abort

Save action input as payload.json. The reviewed plan separates path identifiers, query fields and the HTTP body. Set BYTES_WORKSPACE_ID from granted resource discovery.

Inspect and test this action in the signed action console. A test response still requires the verification below.

Input fields

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "minLength": 1
    },
    "uploadId": {
      "type": "string",
      "minLength": 1
    },
    "scope": {
      "type": "string",
      "enum": [
        "org",
        "private",
        "all"
      ]
    }
  },
  "required": [
    "key",
    "uploadId"
  ],
  "additionalProperties": false
}

Effects

• Aborts the multipart session and its unfinished parts through R2.

Interpret the response

This response does not return a guaranteed canonical target identifier. Keep the discovered request context and interpret its documented values without inventing a resource id.

Confirm the R2 operation succeeded before discarding session details. A local mocked response establishes no live provider state.

The schema describes supported success fields; optional metadata and integration-dependent values may vary. Errors have the exact shapes shown in refused examples.

Success schema:

{
  "type": "object",
  "required": [
    "success"
  ],
  "properties": {
    "success": {
      "type": "boolean"
    }
  }
}

Worked examples

Actual exported Worker handlers with local Miniflare R2/KV. Auth, workspace grants, R2 multipart, notification, usage and semantic integrations are simulated at their configured test boundaries. Synthetic ids, timestamps and signed URLs confer no live access. No deployed provider outcome, external delivery or live grant is established. Upload-session credential values are explicitly redacted; binary responses use the tested SDK transport envelope. Replace synthetic identifiers through credential-scoped discovery. Refused scenarios document failure boundaries; they are not successful workflows.

Successful request

Actual worker response with local Miniflare R2/KV and simulated Auth, workspace grants and outbound integration boundaries. No authorization header is captured.

Input · payload.json:

{
  "key": "organizations/org_acme/workspaces/workspace_acme/big.bin",
  "uploadId": "upload-id-xyz"
}

CLI:

topolo actions validate app_topolo_bytes.uploads.multipart.abort --data @payload.json --json
topolo actions plan app_topolo_bytes.uploads.multipart.abort --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_bytes.uploads.multipart.abort --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_bytes.uploads.multipart.abort",
    "input": {
      "key": "organizations/org_acme/workspaces/workspace_acme/big.bin",
      "uploadId": "upload-id-xyz"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "success": true
}

HTTP 200. Confirm the R2 operation succeeded before discarding session details. A local mocked response establishes no live provider state.

Refused request · HTTP 400

Actual worker response with local Miniflare R2/KV and simulated Auth, workspace grants and outbound integration boundaries. No authorization header is captured.

Input · payload.json:

{
  "key": "big.bin"
}

CLI:

topolo actions validate app_topolo_bytes.uploads.multipart.abort --data @payload.json --json
topolo actions plan app_topolo_bytes.uploads.multipart.abort --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 400:

{
  "error": "Missing key or uploadId"
}

HTTP 400. This request was refused; preserve the exact response and correct its cause before retrying.

Verify the result

• Confirm the R2 operation succeeded before discarding session details. A local mocked response establishes no live provider state.

Errors and recovery

• Missing key or uploadId (HTTP 400): Correct the exact fields using the discovered input schema and prerequisites. Refused input examples demonstrate errors and must not be executed as successful workflows.

Authentication, the action-input validator or resource middleware can refuse a request before this handler. Preserve the exact request id, error and selected credential context. The fixtures establish no live credentials or configured provider.

Recovery boundary

Aborted parts cannot be recovered by this action. Start and upload a new session when needed.

Related actions

• Start multipart upload: Initialize an R2 multipart upload in the selected storage scope and return the scoped key, uploadId and suggested partSize.

Evidence

Actual exported Worker handlers with local Miniflare R2/KV. Auth, workspace grants, R2 multipart, notification, usage and semantic integrations are simulated at their configured test boundaries. Synthetic ids, timestamps and signed URLs confer no live access. No deployed provider outcome, external delivery or live grant is established. Upload-session credential values are explicitly redacted; binary responses use the tested SDK transport envelope. Capture digests and test scenarios are retained in the source fixture records.