Skip to content

Fix direct upload to use account-scoped endpoint#7

Merged
robzolkos merged 1 commit intomasterfrom
fix-direct-upload-account-scoped-path
Dec 11, 2025
Merged

Fix direct upload to use account-scoped endpoint#7
robzolkos merged 1 commit intomasterfrom
fix-direct-upload-account-scoped-path

Conversation

@robzolkos
Copy link
Copy Markdown
Collaborator

Summary

  • Updates the direct upload endpoint to use the account-scoped path required by upstream fix basecamp/fizzy#2079
  • Changes path from /rails/active_storage/direct_uploads to /{account}/rails/active_storage/direct_uploads
  • The fizzy upload file command now works against the production API

Closes #5

Test plan

  • All tests pass (103 runs, 206 assertions)
  • Manually verified fizzy upload file works against production API

The upstream Fizzy API (PR #2079) now requires the account slug in the
direct upload path. Updated to use account_path() for the Active Storage
direct uploads endpoint.

Closes #5
@robzolkos robzolkos merged commit 2a01d93 into master Dec 11, 2025
1 check passed
@robzolkos robzolkos deleted the fix-direct-upload-account-scoped-path branch December 11, 2025 17:25
waynemsmith added a commit to Concurrent-Systems/fizzy-cli that referenced this pull request Mar 28, 2026
uploadFile() returned signed_id (ActiveStorage blob reference) but used
it as the sgid in <action-text-attachment>. The API returns a separate
attachable_sgid field which is the correct ActionText signed global ID.

Also forward direct_upload.headers from the API response instead of
manually constructing them — picks up Content-Disposition header.

Closes basecamp#7

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Direct upload for rich text attachments returns 422 - awaiting upstream fix

1 participant