Skip to content

v1.10.0

Latest

Choose a tag to compare

@alexluong alexluong released this 17 Nov 21:06
· 1 commit to main since this release
86826f1

⚠️ Breaking Changes

See the v1.10 Upgrade Guide for details.

Before you upgrade

  • Set DESTINATIONS_ALLOW_CUSTOM_ENDPOINTS=true if any AWS or GCP Pub/Sub destination sets config.endpoint (LocalStack, the Pub/Sub emulator, S3-compatible storage, VPC endpoints) or any aws_sqs destination has a queue_url that is not an AWS SQS host.
  • Check S3 key_template and Kafka/Kinesis partition_key_template values. They may use field paths, literals, join, to_string, not_null and ||, up to 1024 characters.
  • If you publish events larger than 1 MiB, raise MAX_EVENT_SIZE_BYTES, or set it to 0 for no limit.
  • Check that gcp_pubsub destinations use a service account key.

There is no new migration in this release.

  • Custom endpoints on aws_eventbridge, aws_kinesis, aws_s3, aws_sqs and gcp_pubsub destinations are off unless the operator sets DESTINATIONS_ALLOW_CUSTOM_ENDPOINTS=true. With it off, creating or updating a destination with config.endpoint, or an aws_sqs destination whose queue_url is not an AWS SQS host, is rejected, and existing ones fail each attempt with a validation error that names the field. Leave it off when people outside your organization create destinations. by @alexluong in #1241
  • Events have a size limit, MAX_EVENT_SIZE_BYTES, 1 MiB by default. A larger publish request gets a 413. A larger publish queue message is not redelivered: RabbitMQ and Azure Service Bus reject it (dead-lettered if configured), other brokers ack it and it is deleted. by @alexluong in #1198
  • key_template (aws_s3) and partition_key_template (kafka, aws_kinesis) accept field paths with integer indexes, literals, join, to_string, not_null and ||, up to 1024 characters. Pipes, projections, filters, slices and other functions are rejected on create and update. An existing destination with such a template fails each attempt with a validation error until the template is changed. A Kafka or Kinesis template that is not valid JMESPath still falls back to the event ID as the key, as before. The default S3 template and the templates in the docs are accepted. by @alexluong in #1242, #1243
  • gcp_pubsub destinations accept only service account keys in service_account_json. Other Google credential types are rejected on create and update, and existing destinations that use one fail each attempt with a validation error. by @alexluong in #1246

Features

  • DESTINATIONS_WEBHOOK_FOLLOW_REDIRECTS brings back following redirects on webhook deliveries (up to 10), for deployments whose destinations still answer with a redirect. Off by default, so a 3xx stays a failed attempt as in v1.8. When on, the attempt succeeds or fails on the final response; a 301, 302 or 303 is followed as a GET without the body, and 307 and 308 re-send the POST. by @orshih6 in #1237

Fixes

  • A panic while handling a queue message no longer stops Outpost. The message is nacked, so the queue redelivers it up to its redelivery limit and then dead-letters it, and the panic is logged with its stack. by @alexluong in #1242
  • The Kafka destination uses a new client (franz-go). Memory stays bounded when brokers points at something that isn't Kafka, and a publish that timed out is no longer written after its attempt was recorded as failed. Connection and metadata failures are retried up to 2 times within the attempt. Brokers see client.id outpost, a malformed brokers value is rejected on create and update and fails each attempt on an existing destination, and error messages follow the new client (error codes are unchanged). by @alexluong in #1231
  • Destination filters can be nested up to 16 levels. A deeper filter gets a 422 on create and update; existing filters keep working. by @alexluong in #1244
  • Event and attempt lists on the Postgres log store no longer repeat or skip records at page boundaries. Cursors issued before the upgrade still work. During a rolling upgrade, a node on the previous version answers a new cursor with 400 invalid cursor. by @alexluong in #1223
  • A Kinesis-compatible endpoint that answers PutRecord without a shard ID or sequence number no longer crashes Outpost; the delivery is recorded as a success. by @alexluong in #1228
  • A retry of an MCP event sends the same body as the first attempt. The envelope timestamp is now in milliseconds. by @garethx in #1230
  • A failed attempt caused by a validation error lists the fields that failed, for every destination type. by @alexluong in #1241

Updates

  • Go 1.27.4, amqp091-go v1.16.0 and OpenTelemetry v1.47.0 for security fixes (GO-2026-6859, GO-2026-6700, GO-2026-6615, GO-2026-6508, GO-2026-6348). Log records exported over OTLP name the caller attributes code.function.name, code.file.path and code.line.number (were code.function, code.filepath, code.lineno). by @alexluong in #1233
  • Remaining dependencies updated, including the AWS EventBridge SDK, which was held back for an upstream bug that is now fixed. by @alexluong in #1234
  • Tests and local development run on ClickHouse 26.8. by @alexluong in #1190

New Contributors

Full Changelog: v1.9.0...v1.10.0