Files
windmill/backend/windmill-common
hugocasaandClaude Opus 4.8 bf6be967fa fix: honor verify-ca/verify-full sslmode for postgres connections (#9835)
* fix: enforce tls verification for postgres verify-ca/verify-full sslmode

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: make PG_ACCEPT_INVALID_CERTS value-based and keep cache key well-formed

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: grandfather existing postgres resources via per-resource trust_cert flag

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: scope pg trust_cert migration to resource data, drop schema patch

Hub resource type sync (windmill cache-rt + startup SYNC_CACHED_RT) only touches the admins workspace and is opt-in, so the schema is left to the hub; the migration just grandfathers existing resource values so the upgrade is non-breaking.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: replace pg trust_cert with verify-*-scoped accept_invalid_certs, drop migration

Per-resource accept_invalid_certs (default false for new resources) replaces the trust_cert flag and grandfather migration. It only applies to verify-ca/verify-full; unset falls back to legacy behavior (verify only when a root cert is present) so existing and git-synced resources are not broken on upgrade.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat: warn in job logs when a verify-* postgres resource skips cert verification

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 23:55:11 +02:00
..
2026-06-15 10:23:16 +02:00