From c7ccf29fd02f9db249fb36bc564fcb750542e262 Mon Sep 17 00:00:00 2001 From: Jeff Anderson Date: Tue, 24 Sep 2024 19:03:07 -0400 Subject: [PATCH] Correct postgres retention_period param syntax When trying to use `retention_period` query param with a `postgresql://` URI, this causes a failure. `server error (FATAL: unrecognized configuration parameter "retention_period" (SQLSTATE 42704))` The correct syntax is to include it in the fragment portion of the URI instead. --- docs/pages/includes/config-reference/auth-service.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/includes/config-reference/auth-service.yaml b/docs/pages/includes/config-reference/auth-service.yaml index c3c4ddf383061..19d2e528a3931 100644 --- a/docs/pages/includes/config-reference/auth-service.yaml +++ b/docs/pages/includes/config-reference/auth-service.yaml @@ -63,7 +63,7 @@ teleport: # consume the retention period via a query parameter in the audit_events_uri. See the examples below # for how to configure the retention period for other backends. # Firestore: firestore://events_table_name?eventRetentionPeriod=10d - # Postgres: postgresql://user_name@database-address/teleport_audit?retention_period=10d + # Postgres: postgresql://user_name@database-address/teleport_audit#retention_period=240h retention_period: 365d # minimum/maximum read capacity in units