Replace text content through alias

Outcome

Replace an existing file’s text through the file-content route. It invokes the same content-overwrite handler as files.update, with identical storage and authorization semantics.

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.files.content.update --detail --json
topolo resources topolo-bytes --json
topolo workspaces list topolo-bytes --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.

Request

PUT /api/file-content

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
    },
    "content": {
      "type": "string"
    },
    "bucket": {
      "type": "string",
      "minLength": 1
    },
    "scope": {
      "type": "string",
      "enum": [
        "org",
        "private",
        "all"
      ]
    }
  },
  "required": [
    "key",
    "content"
  ],
  "additionalProperties": false
}

Effects

• Overwrites content, removes the derived thumbnail and schedules thumbnail/index work. Existing sharing records retain their stored paths.

Interpret the response

The response identifier path is $.key for file. An empty list does not discover a target.

Read and compare actual stored bytes and metadata; success alone does not verify completion of background integration work.

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",
    "key",
    "message",
    "contentType"
  ],
  "properties": {
    "success": {
      "type": "boolean"
    },
    "key": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "contentType": {
      "type": "string"
    }
  }
}

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": "documentation.txt",
  "content": "after"
}

CLI:

topolo actions validate app_topolo_bytes.files.content.update --data @payload.json --json
topolo actions plan app_topolo_bytes.files.content.update --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_bytes.files.content.update --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.files.content.update",
    "input": {
      "key": "documentation.txt",
      "content": "after"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "success": true,
  "key": "documentation.txt",
  "message": "File content updated successfully",
  "contentType": "text/plain"
}

HTTP 200. Read and compare actual stored bytes and metadata; success alone does not verify completion of background integration work.

Another supported 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": "alias.txt",
  "content": "fresh"
}

CLI:

topolo actions validate app_topolo_bytes.files.content.update --data @payload.json --json
topolo actions plan app_topolo_bytes.files.content.update --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_bytes.files.content.update --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.files.content.update",
    "input": {
      "key": "alias.txt",
      "content": "fresh"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "success": true,
  "key": "alias.txt",
  "message": "File content updated successfully",
  "contentType": "text/plain"
}

HTTP 200. Read and compare actual stored bytes and metadata; success alone does not verify completion of background integration work.

Refused request · HTTP 403

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": "documentation.txt",
  "content": "after"
}

CLI:

topolo actions validate app_topolo_bytes.files.content.update --data @payload.json --json
topolo actions plan app_topolo_bytes.files.content.update --resource-type workspace --resource-id "$BYTES_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 403:

{
  "error": "Forbidden",
  "message": "Insufficient permissions",
  "required": [
    "files:write",
    "folders:write",
    "sharing:write"
  ],
  "available": [
    "files:read"
  ]
}

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

Verify the result

• Read and compare actual stored bytes and metadata; success alone does not verify completion of background integration work.

Errors and recovery

• Forbidden (HTTP 403): Verify the pinned organization, granted workspace resource and required application permission. Inspect the exact refusal before requesting narrower access; never switch scope to bypass the denial.

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

Preserve old bytes independently and explicitly authorize any restore overwrite. There is no stored revision history in this action.

Related actions

• List files: List one page of files and directories in the verified workspace; eligible files can have derived thumbnails generated during listing.

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.