Skip to content

v1.1.0

Choose a tag to compare

View all tags
@alexluong alexluong released this 24 Jul 15:41
v1.1.0
cfcc320
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Note: No breaking changes and no new migrations in this release. Review the Upgrade to v1.1 guide for behavior changes and deprecations before upgrading.

Features

  • Configurable webhook system header names: pin the exact name of each system header (DESTINATIONS_WEBHOOK_EVENT_ID_HEADER_NAME, _TIMESTAMP_, _TOPIC_, _SIGNATURE_) or set to an empty string to disable it. Deprecates the DESTINATIONS_WEBHOOK_DISABLE_DEFAULT_*_HEADER flags by @ambroziepaval in #992
  • IAM role authentication for AWS SQS: AWS_SQS_ACCESS_KEY_ID and AWS_SQS_SECRET_ACCESS_KEY are now optional; when omitted, Outpost uses the AWS SDK default credential chain (EKS Pod Identity, IRSA, instance profiles) by @ambroziepaval in #996
  • New attempt.success and attempt.failed operator events, emitted once per delivery attempt. If you subscribe with OPERATION_EVENTS_TOPICS=*, note these fire at full delivery throughput — see the upgrade guide before upgrading by @alexluong in #989
  • Delivery retry tasks that repeatedly fail to process now back off exponentially and dead-letter to deliverymq-retry-dlq after 5 receives instead of retrying forever. Tasks stuck in a retry loop before the upgrade drain into the DLQ shortly after upgrading — that's expected and surfaces previously invisible failures by @LendritIbrahimi in #997
  • Stored response body size cap: destination response bodies larger than DESTINATIONS_WEBHOOK_MAX_RESPONSE_BODY_BYTES (default 128 KiB) are replaced with a placeholder so oversized attempt logs can't exceed queue message limits; set 0 to disable by @alexluong in #975
  • Faster log processing: alert evaluation and operator event delivery now run in parallel per destination by @alexluong in #987

Fixes

  • RabbitMQ connections redial automatically after a drop instead of wedging publishing until restart; during a broker outage, publishes fail fast with a 5-second redial cooldown by @LendritIbrahimi in #999
  • exhausted_retries alerts are now suppressed per destination instead of per event, so a high-volume failing destination no longer floods your alert sink by @alexluong in #995
  • Destination topics are normalized on write, so equivalent topic lists compare consistently by @mvanhorn in #994

New Contributors

Full Changelog: v1.0.7...v1.1.0

Contributors

mvanhorn, ambroziepaval, and 2 other contributors
Assets 5
Loading