Skip to content

Release 9.0.41.1

This is the Rolling Release Notes for Release 9.0.41.1. These release notes are applicable only to Privacera's Self Managed version.

Breaking Changes

Monolithic Mode is Now the Default for the Monitoring Stack

  • Impact: This change only affects customers who have enabled the Privacera's monitoring components (Loki/Tempo) and configured it with cloud storage.
  • Default Behavior: Loki/Tempo/Pyroscope are disabled by default. If enabled, it uses local storage by default (no action needed in that case).
  • Action Required: If you have enabled cloud storage for Loki or Tempo, update your values.yml to the new configuration.
  • More Details:

Privacera Monitoring

Added Support for Monolithic Mode for Loki, Tempo, and Pyroscope

Added Support for Monolithic Mode for Loki, Tempo, and Pyroscope

Privacera Portal

Fixed Databricks Unity Catalog Data Explorer Read Time Out

Fixed Databricks Unity Catalog Data Explorer Read Time Out

Fixed an issue where Databricks Unity Catalog displayed “No database found” in Data Explorer, caused by a silent Read Timeout while processing large datasets (over ~5K resources). Connection is now stable and data loads correctly, while other JDBC apps (Postgress, Snowflake, MSSQL) remain unaffected.

Privacera UserSync

Dependency Class Loading Order Update

Dependency Class Loading Order Update

Changed the dependency class loading order to minimize the occurrence of library conflicts that could affect runtime behavior.

Privacera Discovery

Scanning and Reporting for Redshift Views

Scanning and Reporting for Redshift Views

Resolved an issue where scans of Redshift views would fail while the Portal incorrectly reported success. This fix also addresses instances of null or empty table names appearing for specified input or excluded resources. Discovery now scans Redshift views correctly and reports accurate results.

Offline Scan Cleanup Reliability

Offline Scan Cleanup Reliability

Addressed a DynamoDB transaction error ("Transaction request cannot include multiple operations on one item") that caused the offline scan cleanup process to fail when deleting resource classifications. The Offline Scan Cleanup process now completes reliably.

Comments