OffNet Newsroom

Daily topic roundup

Automation / DevOps / IaC

Wednesday, September 23, 2026 · 8 stories, curated & summarized — click any story for the source.

PostgreSQL has launched pgsql-test to enable faster development loops for database logic, addressing the friction developers face when provisioning state and managing transactions. The tool aims to close the gap between application-level testing and database enforcement, which often leads to business rules being pushed into application code. Mocks are insufficient for this purpose as they cannot exercise foreign keys, triggers, row-level security policies, or actual role permissions.

  • Shifting logic back to the database becomes viable when testing is as fast as application code.
  • Mocking fails to validate actual database behaviors like triggers, FKs, and RLS policies.
  • Reduced friction encourages enforcing rules in Postgres rather than application layers.
  • Developers can now get red-green feedback directly within database logic workflows.
TRADE-OFFTesting Database LogicMocking ApproachCannot exercise foreign keysIgnores triggers and policiesMisses role permissionspgsql-test ApproachValidates actual database behaviorExercises foreign keysTests triggers and policiesvs

This article argues that monolithic Cloudflare Workers introduce unnecessary deployment coupling and excessive blast radius at multi-tenant SaaS scales. It proposes a modular architecture leveraging service bindings to decouple components, using image optimization as a concrete example for per-tenant format negotiation and device-aware sizing. The piece also outlines best practices for configuration, testing, and staged releases across different CDN environments.

  • Decouple logic using service bindings to reduce deployment coupling and blast radius.
  • Implement per-tenant format negotiation and device-aware sizing for image optimization.
  • Adopt staged releases and robust testing strategies for modular edge services.
  • Account for multi-CDN differences when designing modular edge architectures.
AWS What's New awsdatabase

Amazon SNS raises message payload limit to 1 MiB

Amazon SNS has increased its maximum message payload size from 256 KiB to 1 MiB, a fourfold expansion. This change allows publishers to send larger data units directly without pre-splitting or offloading, which was previously required for larger workloads. The new 1 MiB limit applies to both Standard and FIFO topics via the MaximumMessageSize attribute.

  • Payload limit increased 4x from 256 KiB to 1 MiB for SNS topics.
  • Applies to both SNS Standard and FIFO topic types.
  • Configure via the new MaximumMessageSize topic attribute.
  • Reduces need to split or offload large messages before publishing.
  • Beneficial for AI, IoT, and app integration workloads with larger data units.
THE SHIFTSNS Payload Limit Grows 4x256KiBPREVIOUS LIMIT1MiBNEW LIMITApplies to Standard and FIFO topics

GitLab has extended its self-hosted AI capabilities to integrate with models deployed via Microsoft Foundry. This update allows organizations to run GitLab Duo development features against AI models hosted within their specific Azure environments. The move provides greater control over model selection and data residency for teams using Azure infrastructure.

  • GitLab Duo Self-Hosted now integrates with Microsoft Foundry deployments
  • Teams can run AI coding tools against models in their own Azure environment
  • Enhances data residency control for organizations using Azure infrastructure
  • Expands available model options for self-hosted GitLab AI workflows
Hacker News (100+ points) general

Trail of Bits: SAML is a fractal of bad design

A new analysis from Trail of Bits characterizes SAML as a structurally flawed protocol where design errors compound at every level. The piece details how legacy XML structures and complex signature verification create persistent security and interoperability risks. It suggests that the protocol's inherent complexity makes it prone to misconfiguration and exploitation by modern attackers.

  • SAML's architectural debt creates compounding security vulnerabilities across implementations.
  • Complex XML signature verification remains a primary source of interoperability failures.
  • Legacy design choices in the protocol resist modern security hardening efforts.
  • Organizations should audit SAML configurations for known structural misconfigurations.
InfoQ generaldevops ↺ since 09-22

Changesets v3 ships ESM-only with 88% smaller install

Changesets v3.0 reduces installation size by 88% by switching to an ESM-only distribution. The release features a rebuilt CLI and updated peer dependency logic that bumps dependents by patch. Migrating to this version requires specific configuration changes.

  • 88% smaller install footprint via ESM-only delivery
  • Peer dependents now bumped by patch to fix prior issues
  • CLI has been completely rebuilt
  • Configuration updates needed for upgrade

CNCF released Kubernetes 1.37, codenamed Garhwal, prioritizing stability, security, and AI/ML workload optimization. The release stabilizes the Metrics API for broader production reliability and introduces rootless Kubelet as a beta feature to enhance security postures. This update signals a shift toward hardened defaults and improved observability for modern containerized deployments.

  • Metrics API moves to stable status, reducing API version churn for monitoring stacks.
  • Rootless Kubelet enters beta, offering a path to run kubelet without root privileges.
  • Release focuses on security hardening and improved support for AI/ML workloads.
  • Stability improvements suggest this is a safe upgrade target for production environments.

Amazon ECS now surfaces live deployment tracking directly within the AWS Management Console, eliminating the need to switch tools for monitoring. The new feature provides a chronological timeline of deployment phases, task lifecycle events, and traffic shift distribution across revisions. This allows engineers to observe health status and diagnose failures in real time for native Linear, Canary, and Blue/Green strategies.

  • Monitor Linear, Canary, and Blue/Green deployments directly in the ECS Console without external tools.
  • View a live timeline of deployment phases, task launches, terminations, and traffic shifts.
  • Diagnose failures and track health status in real time during the rollout process.
  • Consolidate monitoring and troubleshooting workflows into a single interface.
HOW IT WORKSReal-Time ECS Deployment Visibility1Select deployment strategy2Launch task revisions3Shift traffic gradually4Monitor health timeline5Diagnose or rollback
↑