DATABRICKS_ HOST_ URL

Enter the URL where the Databricks environment is hosted.

DATABRICKS_ TOKEN

Enter the Databricks token.

DATABRICKS_ WORKSPACES_ LIST

Add multiple Databricks workspaces to connect to Ranger.

To add a single workspace, add the following default JSON in the text area to define the host URL and token of the Databricks workspace. The text area should not be left empty and should at least contain the default JSON.

Do not edit any of the values in the default JSON.

- alias: DEFAULT
  databricks_host_url: "{{DATABRICKS_HOST_URL}}"
  token: "{{DATABRICKS_TOKEN}}"

To add two workspaces, use the following JSON. {{var}} is an Ansible variable. Such a variable re-uses the value of a predefined variable. Do not change the lowercase property names databricks_host_url and token.

- alias: DEFAULT
  databricks_host_url: "{{DATABRICKS_HOST_URL}}"
  token: "{{DATABRICKS_TOKEN}}"
- alias: "<workspace-2-alias>"
  databricks_host_url: ">workspace-2-url<"
  token: "<dbx-token-for-workspace-2>"

DATABRICKS_ ENABLE

If set to 'true' Privacera Manager will create the Databricks cluster Init s ~/privacera/privacera-manager/output/databricks/ranger_enable.sh

DATABRICKS_ INIT_ SCRIPT_ WORKSPACE_ FLAG_ ENABLE

Set to 'true' for uploading init script into workspace files at location /privacera/<DEPLOYMENT_ENV_NAME>/ranger_enable.sh

DATABRICKS_ MANAGE_ INIT_ SCRIPT

If set to 'true' Privacera Manager will upload Init script ranger_ enable.sh to the identified Databricks Host.

If set to 'false' upload the following two files to the DBFS location. The files are at ~/privacera/privacera-manager/output/databricks.

DATABRICKS_ SPARK_ PLUGIN_ AGENT_ JAR

Use the Java agent to assign a string of extra JVM options to pass to the Spark driver.

Example:

-javaagent:/databricks/jars/privacera-agent.jar

DATABRICKS_ SPARK_ PRIVACERA_ CUSTOM_ CURRENT_ USER_ UDF_ NAME

Property to map logged-in user to Ranger user for row-filter policy. Example: current_user()

See Spark FGAC properties. Check if this property is set in your Databricks cluster. If it is being used, then set its value similar to the PM property. If the value of the PM property and Databricks cluster-level property differ, then it can cause an unexpected behavior.

DATABRICKS_ SPARK_ PRIVACERA_ VIEW_ LEVEL_ MASKING_ ROWFILTER_ EXTENSION_ ENABLE

Property to enable masking, row-filter and data_ admin access on view. This property is a Privacera Manager (PM) property.

Default: true

It is mapped to the Databricks cluster-level property spark.hadoop.privacera.spark.view.levelmaskingrowfilter.extension.enable

See Spark FGAC properties. Check if this property is set in your Databricks cluster. If it is being used, then set its value similar to the PM property. If the value of the PM property and Databricks cluster-level property differ, then it can cause an unexpected behavior.

DATABRICKS_ SQL_ CLUSTER_ POLICY_ SPARK_ CONF

Configure Databricks Cluster policy.

Add the following JSON in the text area:

[
   {
     Note":"First spark conf",
     "key":"spark.hadoop.first.spark.test",
     "value":"test1"
     },
   {
     "Note":"Second spark conf",
     "key":"spark.hadoop.first.spark.test",
     "value":"test2"
     }
]

DATABRICKS_ POST_ PLUGIN_ COMMAND_ LIST

This property is not included in the default YAML file, but can be added if required.

Use this property if you want to run a specific set of commands in the Databricks init script.

The following example is added to the cluster init script to allow Athena JDBC via data access server:

sudo iptables -I OUTPUT 1 -p tcp -m tcp --dport 8181 -j ACCEPT ;
sudo curl -k -u user:password {{PORTAL_URL}}/api/dataserver/cert?type=dataserver_jks \
       -o /etc/ssl/certs/dataserver.jks 
sudo chmod 755 /etc/ssl/certs/dataserver.jks
            

DATABRICKS_ SPARK_ PYSPARK_ ENABLE_ PY4J_ SECURITY

With this property you blacklist Pyspark APIs to enable security. This is a Privacera Manager (PM) property

It is mapped with the Databricks cluster-level property spark.databricks.pyspark.enablePy4JSecurity.

See Spark FGAC properties. Check if this property is set in your Databricks cluster. If it is being used, then set its value similar to the PM property. If the value of the PM property and Databricks cluster-level property differ, then it can cause an unexpected behavior.