Conversation
Add support for publishing events to Cloudflare Queues via their HTTP API. Implements #655 - Add destcfqueues Go provider with Publish, Validate, and ComputeTarget - Add provider metadata (metadata.json and instructions.md) - Update OpenAPI spec with CloudflareQueues schemas - Add user documentation (cloudflare-queues.mdx) - Register provider in default.go - Add validation and publish unit tests - Add SDK test factory and integration tests
…rors as failed attempts
alexluong
force-pushed
the
feat/cloudflare-queues-destination
branch
from
September 28, 2026 16:51
8e4a350 to
74c972b
Compare
alexluong
marked this pull request as ready for review
September 28, 2026 16:51
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Cloudflare Queues as a destination type. Each event is pushed with one request to Cloudflare's
POST /accounts/{account_id}/queues/{queue_id}/messagesas{"body": {"data": …, "metadata": …}, "content_type": "json"}, authenticated with an API token that has Account > Queues > Edit (Queues Write).Continues #657 by @Swahjak, whose commit is kept as the first commit. The commits after it rebase onto current main (shared HTTP client from #1021, format errors as failed attempts from #957,
DestinationUpdatediscriminator), fix the API payload and response handling, and correct the docs against the live API. Closes #655. Supersedes #657.Behavior
account_idandqueue_idmust be 32-character lowercase hex, which is how Cloudflare shows them. Cloudflare rejects queue names, dashed UUIDs and uppercase IDs on every push, so Outpost rejects them with a 422 when the destination is created or updated.success: false, is a failed attempt that keeps Cloudflare's error code and message. A token without Queues Write gets the same 401 "Authentication error" as an invalid token. Cloudflare doesn't return a 403 for it.data/metadatawrapper. Larger events fail with 413 and aren't checked before sending, same as SQS, Kinesis and Pub/Sub.DestinationTypeenum also gainskafka, which was missing. This changes the generated SDK enums.Tests
The fixtures in
destcfqueues_publish_test.goare real Cloudflare responses (success, 401, 400, 404, 413, 500) recorded against a live queue, with IDs scrubbed.TestCloudflareQueuesDestination_Validatecovers the ID format.Tested manually against a real queue: publish and read back through a pull consumer, bad token, token without Queues Write, bad account and queue IDs, partial PATCH, and an oversize event.
SDK regen and the
spec-sdk-testscontract test come in a follow-up after merge.🤖 Generated with Claude Code