[pull] main from hookdeck:main#152
Merged
Merged
Conversation
…t DLQ (#957) * fix(destregistry): treat event format errors as failed deliveries, not DLQ A Format/key-template failure (e.g. an S3 key_template referencing a field absent from the event) returned a nil delivery, which the registry turned into a nil attempt and the deliverymq handler classified as a PreDeliveryError → nack → Pub/Sub DLQ. The failure was never logged, invisible to the customer, and paged us instead of surfacing as an actionable delivery error. Add destregistry.NewFormatErrorDelivery, returning a non-nil failed Delivery plus an ErrDestinationPublishAttempt, so the registry records a failed attempt, acks the message, and retries via the scheduler. The customer-facing response is a generic message; the raw Go error stays on the error for logs/telemetry and is not persisted on the attempt. Apply it across all providers with a Format step: s3, sqs, azure_servicebus, gcp_pubsub, webhook, webhook_standard (previously `return nil, err`) and kinesis, kafka (previously nil-delivery ErrDestinationPublishAttempt). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * test(e2e): regression for format error delivered as failed attempt, not DLQ Standalone e2e test reproducing the production incident: an aws_s3 destination whose key_template references a field missing from the event. Asserts the fixed behavior end to end — nothing is written to S3, each delivery is recorded as a failed attempt carrying the format error, and retries run on the normal schedule and exhaust their budget rather than being nacked/dead-lettered. Verified as a real guard: reverting the destawss3 fix makes this test fail (0 attempts logged, message dead-lettered) instead of recording 3 attempts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(destregistry): rename NewFormatErrorDelivery to NewFormatError The helper returns the (*Delivery, error) pair a publisher returns on a format failure, not just a delivery — name it accordingly. Behavior unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(e2e): trim format-error regression test comment Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* `Outpost.Configuration.GetManagedConfig()`: `response` **Changed** (Breaking⚠️ ) * `Outpost.Configuration.UpdateManagedConfig()`: * `request.Request` **Changed** (Breaking⚠️ ) * `response` **Changed** (Breaking⚠️ ) Co-authored-by: speakeasybot <bot@speakeasyapi.dev>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* `outpost.configuration.get_managed_config()`: `response` **Changed** (Breaking⚠️ ) * `outpost.configuration.update_managed_config()`: * `request` **Changed** (Breaking⚠️ ) * `response` **Changed** (Breaking⚠️ ) Co-authored-by: speakeasybot <bot@speakeasyapi.dev>
* `outpost.configuration.getManagedConfig()`: `response` **Changed** (Breaking⚠️ ) * `outpost.configuration.updateManagedConfig()`: * `request` **Changed** (Breaking⚠️ ) * `response` **Changed** (Breaking⚠️ ) Co-authored-by: speakeasybot <bot@speakeasyapi.dev>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )