feat(soa-postgres): CA-bundle ssl object + publish 0.1.2 (self-heal)#107
Merged
Conversation
Widen `ssl` from `boolean` to `boolean | PostgresSslConfig` across PostgresPoolConfig, PostgresProvider, and PostgresProviderSchema so a consumer can pin a CA bundle (e.g. the Amazon RDS roots, which aren't in Node's default trust store) instead of a bare `true`. pg forwards the object verbatim to tls.connect; no behavior change for `true`/`false`. Bumps 0.1.1 -> 0.1.2 so the push-to-main auto-publish ships this together with the already-merged PostgresProvider self-heal (keepAlive + idle-client error handler) that 0.1.1 predates.
❌ Test Results
Package Results
Commits
LinksUpdated: 2026-06-01T22:06:17.729Z |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Two things, so
@saga-ed/soa-postgresis ready for rostering iam-api (PR saga-ed/rostering#359) to consume:Widen
sslto accept a CA-bundle object.sslgoes frombooleantoboolean | PostgresSslConfigacrossPostgresPoolConfig(loader output),PostgresProvider, andPostgresProviderSchema.pgforwards the object verbatim totls.connect, so a consumer can pin the Amazon RDS CA bundle (which isn't in Node's default trust store) instead of a baretrue. No behavior change fortrue/false.Bump
0.1.1 → 0.1.2. The push-to-main auto-publish (publish-all-packages.yml) only republishes when the version is new — it skips when the version already exists.0.1.1was published 2026-05-27, butd432357(PostgresProvider self-heal: idle-client'error'handler +keepAlive) andfa9ef25(route the IAM/RDS path through the provider) landed afterward and kept the version at0.1.1, so they never shipped. Bumping to0.1.2ships them — plus the ssl change above — on merge.Why
iam-api #359 wires prod RDS auth through
@saga-ed/soa-postgres. To route its three pools throughPostgresProvider(and inherit the self-heal so an RDS failover can't crash the process as an uncaught exception), it needs (a) a published version that actually contains the self-heal, and (b) the provider to accept a CA-bundlesslobject so the existing RDS CA pinning survives the move off hand-rolledpg.Pools.Verification
tsc --noEmit✅,tsupbuild ✅vitest✅ 30 tests (added 2: CA-bundlesslobject passes through topgon both thePostgresPoolConfigand static-schema paths)After merge
Merging triggers the
0.1.2publish; then rostering #359 repins to0.1.2, regenerates its lockfile, and adoptsPostgresProvider.