When an email notification contains a link to a comment, clicking the link now correctly navigates to and displays the comment.
Added a flag to mark log files that might contain sensitive information.
You can now assign the Timestamp Shift generator to primary key columns, including columns that are part of a composite primary key.
When writing destination data to a container repository, based on the size of the source database, Tonic attaches resource requests to the datapacker pod to verify that the cluster has sufficient resources for the data.
Tonic now supports writing destination data to container registries on Amazon Elastic Container Registry (Amazon ECR).
Fixed an issue where users could not assign access to permission sets when they did not have access to create and manage custom permission sets.
For foreign keys that have multiple primary keys, Tonic now prevents data generation if the assigned generation configuration for the primary key columns is inconsistent.
Standardized the display format of the heading area of the workspace management views.
File connector
- Fixed an issue with deleting multiple files from a file group.
MongoDB
- From Privacy Hub, you can now use the option to review and apply recommended generators to all of the detected sensitive fields.
- When there are schema changes that are not yet scanned, such as a new collection or new fields in a collection, they are now handled as Passthrough. The schema changes no longer cause data generation to fail.
MySQL
- You can now configure a MySQL workspace to write the destination data to a container repository.
PostgreSQL
- Fixed an issue where when an excluded schema did not exist in the source database, the test connection option returned an error.
- Customers are now by default automatically enrolled in Data Pipeline V2 mode, and do not see the option to enable or disable it. The ability to enable or disable Data Pipeline V2 is granted to individual customers as needed.
Snowflake
- Fixed an issue where when an excluded schema did not exist in the source database, the test connection option returned an error.
