From 6880f5ec97465385b9666782b74b1e5c58527e10 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Thu, 28 Nov 2024 12:14:53 +0100 Subject: [PATCH] Clarify configuration opt-out instructions in audit logging guide (#1475) See #1446 Co-authored-by: Christian Georgi --- guides/data-privacy/audit-logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/data-privacy/audit-logging.md b/guides/data-privacy/audit-logging.md index a20682adf..b44dcdc1f 100644 --- a/guides/data-privacy/audit-logging.md +++ b/guides/data-privacy/audit-logging.md @@ -490,4 +490,4 @@ This provides an ultimate level of resiliency, plus additional benefits: - **False log messages are avoided** — messages are forwarded to the audit log service on successfully committed requests; and skipped in case of rollbacks. -This transparently applies to all implementations, even [custom implementations](#custom-implementation). You can opt out of this default by configuring cds.audit-log.[development].outbox = false, for example, as we do in the default configuration for the `development` profile. +This transparently applies to all implementations, even [custom implementations](#custom-implementation). You can opt out of this default by configuring cds.audit-log.[development].outbox = false.