WPB-20207 add audit logging and metadata storage to asset upload (#4782)

Author: battermann

changelog.d/2-features/WPB-20207

@@ -0,0 +1 @@
+cargohold: add asset audit logging on upload

charts/cargohold/templates/configmap.yaml

@@ -55,6 +55,7 @@ data:
       {{- if .downloadLinkTTL }}
       downloadLinkTTL: {{ .downloadLinkTTL }}
       {{- end }}
+      assetAuditLogEnabled: {{ .assetAuditLogEnabled }}
       federationDomain: {{ .federationDomain }}
       disabledAPIVersions: {{ toJson .disabledAPIVersions }}
       {{- end }}

charts/cargohold/values.yaml

@@ -30,6 +30,7 @@ config:
   settings:
     maxTotalBytes: 104857632 # limit to 100 MiB + 32 bytes
     downloadLinkTTL: 300 # Seconds
+    assetAuditLogEnabled: false
     # Disable one ore more API versions. Please make sure the configuration value is the same in all these charts:
     # brig, cannon, cargohold, galley, gundeck, proxy, spar.
     disabledAPIVersions: [ development ]

docs/src/developer/reference/config-options.md

@@ -1231,6 +1231,10 @@ Link to diagram:
 https://mermaid.live/edit#pako:eNrdVbFu2zAQ_ZUDJ7ewDdhtUkBDgBRB0CHIYCNL4eVEnmWiMk8lKbttkH8vJbsW5dCOUXSqBkHiPT6-e3yinoVkRSITEC5H32syku40FhbXCwP7C6VnC1hqSQNL6l1XeWRPwBuKqxk8OXKwpRyrahxGxvQD11VJY8mvSHPOB4UlMknSrtonbcfStBVar6Wu0HjQJgCdGwUNKfaonMGMax8WeH9acIq5FXKOuwVE7BcqN4U2v9IlibbgFZcqXZ5_ABeMxYK6uiXpwRb5YHp1NYTJ9FN7ixw3jW6ri5UHXva28rZ5BsVbUzIqB-gc-WgTD9DRzU3Pz7v9FChZYnk8L4KGiW23Gdyz3aJVQW7IoYvQbT3gDq2_wsIIbpWCr6MvHF5WhIpsL2p6g6HFhHePvdajFR6Yv0Fd7ZTDquF9mj3AMoR2t0zHcZg1CiJj92akdGP-OLBJ9JpDFOa73YGNxnRAFZ3Te9rxey5L3gZHdmueMrsLyBnHDwpScerGQr_9dn1tzfFeR_2k2MioRFIn15MhTD82Sb0-ndT4fPjM-emcdsDItf23eVlSW_D_ltXYv0uzenTknU_rOd_fzOsfy_9xYvtN_21ixVCsya5Rq_D3fG6KC-FXtKaFyMKjoiXWpV-IhXkJUKw9z38aKTJvaxqKulKBff-jFdkSS0cvvwHKl250
 -->
 
+Audit logging
+
+- `settings.assetAuditLogEnabled` (boolean): enables asset upload/download audit logging and metadata collection on the backend. Intended for enterprise/on‑prem deployments; should remain disabled on cloud. Default: `false`.
+
 ### Galley
 
 For conversation invite links to be correct in a multi-ingress setup `settings.multiIngress` needs to be configured as map from `Z-Host` to the conversation URI prefix.  This setting is a `Z-Host` depended version of `settings.conversationCodeURI`. In fact `settings.multiIngress` and `settings.conversationCodeURI` are mutually exclusive.

hack/helm_vars/wire-federation-v0/values.yaml.gotmpl

@@ -152,6 +152,7 @@ cargohold:
     enableFederation: true # keep in sync with brig.config.enableFederation, galley.config.enableFederation and tags.federator!
     settings:
       federationDomain: federation-test-helper.wire-federation-v0.svc.cluster.local
+      assetAuditLogEnabled: false
   secrets:
     awsKeyId: dummykey
     awsSecretKey: dummysecret

hack/helm_vars/wire-server/values.yaml.gotmpl

@@ -252,6 +252,7 @@ cargohold:
     settings:
       # See helmfile for the real value
       federationDomain: integration.example.com
+      assetAuditLogEnabled: false
       disabledAPIVersions: []
   secrets:
     awsKeyId: dummykey

integration/integration.cabal

@@ -118,7 +118,6 @@ library
     Test.Brig
     Test.Cargohold.API
     Test.Cargohold.API.Federation
-    Test.Cargohold.API.Util
     Test.Cargohold.API.V3
     Test.Cargohold.Metrics
     Test.Cells