feat(cache): add postgres ssl-mode to PostgresConfig (TLS support)#13
Merged
Conversation
The Postgres cache adapter builds an r2dbc connection that defaults to SSLMode.DISABLE, so servers enforcing TLS (e.g. AWS Aurora with rds.force_ssl) reject it with 'no pg_hba.conf entry ... no encryption'. Add a typed firefly.cache.postgres.ssl-mode (FIREFLY_CACHE_POSTGRES_SSL_MODE), default 'disable' for back-compat, mapped to the driver in fireflyframework-cache-postgres. RedisConfig already has an ssl flag; this brings the Postgres adapter to parity.
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
2 participants
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.
Problema
El adaptador de cache Postgres construye la conexión r2dbc con SSLMode.DISABLE por defecto → servidores que exigen TLS (AWS Aurora con rds.force_ssl) la rechazan: 'no pg_hba.conf entry ... no encryption'. Visto en vivo en firefly-dev (pod flydocs-auth-middleware; session-store muerto pese a pod Healthy).
Cambio
Añade firefly.cache.postgres.ssl-mode (env FIREFLY_CACHE_POSTGRES_SSL_MODE) a PostgresConfig, default 'disable' (back-compat). El mapeo al driver va en el PR hermano de fireflyframework-cache-postgres (usa cfg.getSslMode()). RedisConfig ya tenía ssl; paridad.
Release
Lockstep (${project.version}). El campo (este PR) debe releasearse antes/junto con el mapeo.
Causa raíz verificada: el builder llama host/port/database/username/password/schema/options pero nunca .sslMode().