NOTE: Releases v692 through v695 were removed.
Update to PII detection - PII container removed
As of v697, updated how Tonic performs PII detection. The name detection process now also scans for international names with origins from 103 different countries.
The PII detection process now runs from the Tonic worker instead of in a separate container.
To avoid errors when you upgrade, future versions up to v999 will have a placeholder PII container. The container is not active and is not used to run Tonic.
Before you upgrade to V1000 or later, you must remove the PII container from your instance.For a Docker deployment, in docker-compose.yaml, remove the tonic_pii_detection section.
For a Kubernetes deployment:
- Remove the file tonic-pii-detection-deployment.yaml.
- Remove the file tonic-pii-detection-service.yaml.
- Update tonic-worker-deployment.yaml to remove the entry for
TONIC_PII_DETECTION_URL. - Update values.sample.yaml to remove the entry for
pii_detection.
If you do not remove the PII container before you upgrade to v1000 or later, then when you upgrade Tonic, you will encounter image pull errors.
Other updates
Improved error messaging on the Tonic UI for failed data generation jobs.
Reduced the telemetry logging for PII detection during sensitivity scans to reduce the performance impact on self-hosted instances with machines that do not have internet access.
Fixed an issue that prevented users from configuring the Random Timestamp generator Date Format when the generator was selected as a sub-generator of the JSON Mask and other composite generators.
Made a minor correction to a data generation log message.
Reduced Tonic slowdowns caused by telemetry.
MySQL
- Fixed an issue that caused data connections to fail with the error
The ConnectionString property has not been initialized. - Fixed an issue where chained foreign keys caused subsetting jobs to fail.
Oracle
- Fixed an issue where long column names caused data generation to return the error
ORA-00972: identifier is too long. - Fixed an issue where chained foreign keys caused subsetting jobs to fail.
PostgreSQL
- Fixed an issue where chained foreign keys caused subsetting jobs to fail.
SQL Server
- Users can now assign generators to timestamp and rowversion columns.
- Fixed an issue where a database ID mismatch in the master and database tables prevented data generation from starting.
- Fixed an issue where chained foreign keys caused subsetting jobs to fail.
