Customize Topic and Tables names

By default, topic and table names are assigned and managed internally by Privacera Discovery. Also, the deployment environemnt name is attached as a suffix to the topic and table names.

For example, the default name for a Classification Topic in Privacera Discovery is shown as below:

CLASSIFICATION_TOPIC: "privacera_classification_info_{{DEPLOYMENT_ENV_NAME}}"

To customize the name of a topic or table, you can do one of the following:

• Remove the {{DEPLOYMENT_ENV_NAME}} variable as suffix.
• Re-define a new topic/table name.

If you want to customize any topic or table name, refer to the property in the the following table:

Property	Description	Example
PRIVACERA_PORTAL_TOPIC_DYNAMIC_PREFIX	Uncomment and enter a custom name to add a prefix to the real-time topic for Data Sources in Privacera Portal.	PRIVACERA_PORTAL_TOPIC_DYNAMIC_PREFIX="privacera_scan_worker"
CLASSIFICATION_TOPIC ALERT_TOPIC SPARK_EVENT_TOPIC RESULT_TOPIC OFFLINE_SCAN_TOPIC AUDITS_TOPIC SCAN_RESOURCE_INFO_TOPIC RIGHT_TO_PRIVACY_TOPIC DELAY_QUEUE_TOPIC APPLY_SCHEME_TOPIC ML_CLASSIFY_TAG_TOPIC LINEAGE_TOPIC	You can customize the topic names. Uncomment the topic, and enter a name, along with the {{DEPLOYMENT_ENV_NAME}} as the suffix. To remove the {{DEPLOYMENT_ENV_NAME}} as the suffix, refer to the DISCOVERY_DEPLOYMENT_SUFFIX_ID property in this table. {{DEPLOYMENT_ENV_NAME}} is the name of the environment you have given in the vars.privacera.yml	CLASSIFICATION_TOPIC: "privacera_classification_info_{{DEPLOYMENT_ENV_NAME}}" ALERT_TOPIC: "privacera_alerts_{{DEPLOYMENT_ENV_NAME}}" SPARK_EVENT_TOPIC: "privacera_spark_events_{{DEPLOYMENT_ENV_NAME}}" RESULT_TOPIC: "privacera_results_{{DEPLOYMENT_ENV_NAME}}" OFFLINE_SCAN_TOPIC: "privacera_offline_scan_{{DEPLOYMENT_ENV_NAME}}" AUDITS_TOPIC: "privacera_audits_{{DEPLOYMENT_ENV_NAME}}" SCAN_RESOURCE_INFO_TOPIC: "privacera_scan_resources_info_{{DEPLOYMENT_ENV_NAME}}" RIGHT_TO_PRIVACY_TOPIC: "privacera_right_to_privacy_{{DEPLOYMENT_ENV_NAME}}" DELAY_QUEUE_TOPIC: "privacera_delay_queue_{{DEPLOYMENT_ENV_NAME}}" APPLY_SCHEME_TOPIC: "privacera_apply_scheme_{{DEPLOYMENT_ENV_NAME}}" ML_CLASSIFY_TAG_TOPIC: "privacera_ml_classify_tag_{{DEPLOYMENT_ENV_NAME}}" LINEAGE_TOPIC: "privacera_lineage_{{DEPLOYMENT_ENV_NAME}}"
RESOURCE_TABLE ALERT_TABLE SCAN_REQUEST_TABLE ACTIVE_SCANS_TABLE MLRESOURCE_TABLE LINEAGE_TABLE AUDIT_SUMMARY_TABLE STATE_TABLE SCAN_STATUS_TABLE	You can customize the table names. Uncomment the table, and enter a name, along with the {{DEPLOYMENT_ENV_NAME}} as the suffix. To remove the {{DEPLOYMENT_ENV_NAME}} as the suffix, refer to the DISCOVERY_DEPLOYMENT_SUFFIX_ID property in this table.	RESOURCE_TABLE: "privacera_resource_v2_{{DEPLOYMENT_ENV_NAME}}" ALERT_TABLE: "privacera_alert_{{DEPLOYMENT_ENV_NAME}}" SCAN_REQUEST_TABLE: "privacera_scan_request_{{DEPLOYMENT_ENV_NAME}}" ACTIVE_SCANS_TABLE: "privacera_active_scans_{{DEPLOYMENT_ENV_NAME}}" MLRESOURCE_TABLE: "privacera_mlresource_v2_{{DEPLOYMENT_ENV_NAME}}" LINEAGE_TABLE:"privacera_lineage_{{DEPLOYMENT_ENV_NAME}}" AUDIT_SUMMARY_TABLE: "privacera_audit_summary_{{DEPLOYMENT_ENV_NAME}}" STATE_TABLE: "privacera_state_{{DEPLOYMENT_ENV_NAME}}" SCAN_STATUS_TABLE: "privacera_scan_status_{{DEPLOYMENT_ENV_NAME}}"
DISCOVERY_DEPLOYMENT_SUFFIX_ID	Use this property to remove the {{DEPLOYMENT_ENV_NAME}} variable as suffix from the topic/table names. Note: This is a custom property, and has to be added separately to the YAML file.	DISCOVERY_DEPLOYMENT_SUFFIX_ID: ""
DISCOVERY_BUCKET_SQS_NAME	You can customize the SQS bucket name. Uncomment the table, and enter a name, along with the {{DISCOVERY_DEPLOYMENT_SUFFIX_ID}} as the suffix.	DISCOVERY_BUCKET_SQS_NAME: "privacera_bucket_sqs_{{DISCOVERY_DEPLOYMENT_SUFFIX_ID}}"