Repository navigation
events: SQS, Azure Queue and R2 Queue sources; events setup - #55
Merged
Merged
Conversation
New pull-based hint sources for `pail events`, one per service's queue: --sqs-queue (S3 notifications or EventBridge, SigV4), --azure-queue (Event Grid -> Storage Queue), --r2-queue ACCOUNT/QUEUE (Cloudflare Queues HTTP pull). Also PAIL_EVENTS_SOURCE and a store-config `events.<url>.source`. A notification stays a nudge: a message that does not parse is logged and becomes Hint::Scan (a full re-list); a message is deleted only after its events are out and the cursor is saved. `pail events setup --consumer NAME` prints the gcloud/aws/az/wrangler commands that wire refs/ and .actions/ into a per-consumer queue; --apply runs them after a y/N question (--yes skips it). No model change: every source is the model's notification (verify/README.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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 three bucket-notification sources to
pail eventsand apail events setupcommand. A notification is still only a nudge; the watcher re-reads, the safety poll covers losses.Sources
--sqs-queue URLAWS_*env, thenaws configure export-credentials)--azure-queue URLBlobCreated/BlobDeleted(Event Grid or CloudEvents schema, JSON or base64); SAS in the URL or a provider token--r2-queue ACCOUNT/QUEUECLOUDFLARE_API_TOKENor provider tokenPAIL_EVENTS_SOURCE=sqs:URL(gcs:,azure:,r2:,poll) and config[events "s3://acme/app"] source = …. Order: flag, env, config, poll.Hint::Scan(full re-list). Never dropped silently. Wrong bucket/prefix: deleted, ignored.pail events setup --consumer NAMEPrints gcloud / aws / az / wrangler commands for
<repo>/refs/and<repo>.actions/intopail-NAME. Print-only by default.--applyasks y/N (--yesskips) and refuses while a placeholder is unresolved. Not run by the author.Model
No change. Every source is the model's notification; unparseable = the safety-poll scan; delete =
finish(needsemittedandsaved). Written up inverify/README.md.Tests
--yes, stop on failure, placeholders refused).cargo fmt --check,cargo test --release,npm run check,npm testpass.ci.ymlunchanged.🤖 Generated with Claude Code