### Example installation command with Google Artifact Registry Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_google-artifact-registry.htm Example of running the installation script with the registry URL, user _json_key, and path to the JSON key file. ```bash sudo sh install-master.sh properties.yaml -r registries.yaml \ --registry-url https://europe-west1-docker.pkg.dev/path/to/registry \ --registry-user _json_key \ --registry-pass /path/to/json_key_file.json ``` -------------------------------- ### Example installation command with access token Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_azure-registry.htm Example command for installing an Edge site using access token authentication with Azure Container Registry. Shows the format for the registry URL, user, and password. ```bash sudo sh install-master.sh properties.yaml -r registries.yaml \ --registry-url edge.azurecr.io/myazurefolder \ --registry-user azureEdge \ --registry-pass azureEdge12 ``` -------------------------------- ### Example installation with Azure IAM authentication Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_azure-registry.htm Example command for installing an Edge site using Azure IAM-based authentication with an Azure Container Registry. Replace the registry URL with your own. ```bash ./edgecli install \ --registry-url edge.azurecr.io/myazurefolder ``` -------------------------------- ### Example edgecli install command with Service Account Key Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_google-artifact-registry.htm Example command showing how to install an Edge site using the Service Account Key authentication with a Google Artifact Registry. Replace the URL and file path with your own values. ```bash ./edgecli install \ --helm-url oci://europe-west1-docker.pkg.dev/path/to/registry \ --helm-user _json_key \ --helm-pass /path/to/json_key_file.json ``` -------------------------------- ### Example Edge site installation with ECR Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_amazon-elastic-registry.htm Example command showing how to install an Edge site with a specific ECR registry URL and custom folder. The URL includes the AWS account ID, region, and repository path. ```bash ./edgecli install --registry-url 812518457384.dkr.ecr.eu-west-1.amazonaws.com/myawsfolder ``` -------------------------------- ### Example edgecli install command with registry URL Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_google-artifact-registry.htm Example installation command for an Edge site using Workload Identity Federation for GKE. The `--registry-url` flag specifies the registry URL, here `https://europe-west1-docker.pkg.dev/path/to/registry`. ```bash ./edgecli install \ --registry-url https://europe-west1-docker.pkg.dev/path/to/registry ``` -------------------------------- ### Edge CLI install command with flags Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_install-edge-site.htm Example of the Edge CLI installation command with flags for OpenShift, private registry URL, and registry credentials. Add flags to configure your setup, such as for a forward proxy. ```bash ./edgecli install -n edge-namespace --is-openshift --registry-url https://private-docker.registry.com --registry-user user1 --registry-pass pass12 ``` -------------------------------- ### Access token authentication example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_azure-registry.htm Example command for installing an Edge site using an Azure Container Registry access token. It uses the registry URL 'oci://edge.azurecr.io/myazurefolder', token name 'azureEdge', and token password 'azureEdge12'. ```bash ./edgecli install --helm-url oci://edge.azurecr.io/myazurefolder \ --helm-user azureEdge \ --helm-pass azureEdge12 ``` -------------------------------- ### Edge CLI Install with OpenShift and Registry Flags Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Example edgecli install command with flags for OpenShift and a private registry. Add flags to ./edgecli install -b backup.yaml. ```bash ./edgecli install -b backup.yaml --is-openshift --registry-url https://private-docker.registry.com --registry-user user1 --registry-pass pass12 ``` -------------------------------- ### Example: Authenticate with Nexus registry Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_user-pass-registry.htm Example command flags for authenticating with a Nexus registry using username and password. ```bash --registry-url nexus.company.com/edge-registry \ --registry-user NexusEdge \ --registry-pass NexusEdge12 ``` -------------------------------- ### Example: Create Azure Key Vault with Workload Identity (Bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-azure-key-vault.htm Example command for bundled k3s clusters. Uses sudo with edgecli. Example values: Azure-workload-identity, Azure Key vault with workload identity authentication., AZ_22, 165. ```bash sudo ./edgecli vault create azure workload-identity Azure-workload-identity \ --desc Azure Key vault with workload identity authentication. \ --clientId AZ_22 --tenantId 165 ``` -------------------------------- ### Verify CLI setup Source: https://productresources.collibra.com/docs/collibra/latest/Content/CLI/ta_set-up-cli.htm Commands to run `collibra info` to confirm the CLI setup was successful. ```Windows .\collibra info ``` ```Mac and Linux ./collibra info ``` -------------------------------- ### Install Edge site with private Docker registry Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Example of the edgecli install command with flags for a private Docker registry, including registry URL, username, and password. ```bash ./edgecli install \ --registry-url https://private-docker.registry.com \ --registry-user user1 \ --registry-pass pass12 ``` -------------------------------- ### Example proxy command with hostname and port Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/co_connecting-to-a-proxy-server.htm Example command using a proxy with hostname proxy.example.com and port 443. Note the missing dash before Dhttps.proxyUser in the source. ```bash bin/lineage-harvester -Dhttps.proxyHost=proxy.example.com -Dhttps.proxyPort=443 Dhttps.proxyUser=myusername -Dhttps.proxyPassword=mypassword ``` -------------------------------- ### krb5.conf example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/RegisterDataSource/Authentication/co_kerberos-auth.htm Example Kerberos configuration file with default realm, ticket lifetime, and logging settings. Replace placeholders like and with actual values. ```plaintext [libdefaults] renew_lifetime = 7d forwardable = true default_realm = MY.REALM ticket_lifetime = 24h dns_lookup_realm = false dns_lookup_kdc = false default_ccache_name = /tmp/krb5cc_%{uid} [logging] default = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log kdc = FILE:/var/log/krb5kdc.log [realms] MY.REALM = { kdc = admin_server = } ``` -------------------------------- ### Example: Create Azure Key Vault with Workload Identity (Managed Kubernetes) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-azure-key-vault.htm Example command for managed Kubernetes clusters. Uses edgecli without sudo. Example values: Azure-workload-identity, Azure Key vault with workload identity authentication., AZ_22, 165. ```bash ./edgecli vault create azure workload-identity Azure-workload-identity \ --desc Azure Key vault with workload identity authentication. \ --clientId AZ_22 --tenantId 165 ``` -------------------------------- ### Create Azure Key Vault with PFX certificate (bundled k3s) - example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-azure-key-vault.htm Example command for bundled k3s that creates a vault instance named 'Azure-service-principal-PFX' with a PFX certificate. It uses the default DNS suffix 'vault.azure.net' and example credentials. ```bash sudo ./edgecli vault create azure sp-secret Azure-service-principal-PFX \ --desc Azure Key vault with service principal with PFX cert authentication. \ --dnsSuffix vault.azure.net \ --tenantId 165 \ --clientId AZ_22 \ --certPath ~/azurekey/vault/edge-site.pfx \ --certPassword AZ_PFX_password1 ``` -------------------------------- ### Example: Authenticate with JFrog Helm registry Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_user-pass-registry.htm Example command flags for authenticating with a JFrog Helm registry using username and password. ```bash --helm-url jfrog.company.com/artifactory/edge-registry \ --helm-user jfrogEdge \ --helm-pass jfrogEdge12 ``` -------------------------------- ### Verify all pods are installed and running Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_install-edge-site.htm Run this command to ensure the state of all pods are installed and running. ```bash sudo /usr/local/bin/kubectl get pods --all-namespaces ``` -------------------------------- ### Create AWS instance-profile vault example (bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-aws-secret-manager-vault.htm Example command for creating an AWS instance-profile vault on bundled k3s with a specific name, description, region, and endpoint override. ```bash sudo ./edgecli vault create aws instance-profile AWS-Instance \ --desc=AWS vault with Instant Profile authentication \ --region=eu-west-1 \ --endpointOverride=http://my-secret-vault.aws.com ``` -------------------------------- ### Example PEM file Source: https://productresources.collibra.com/docs/collibra/latest/Content/Console/Infrastructure/DGCService/SecurityConfiguration/ta_configure-custom-certificate-for-sso-cdic.htm Example of a PEM file containing the server certificate and private key, as required for the custom certificate. ```text -----BEGIN RSA PRIVATE KEY----- MIIEvgIBADA ... bml6YXRpb252YWxza .... z3P668YfhUbKdRF6S42Cg6zn -----END RSA PRIVATE KEY----- # Your certificate -----BEGIN CERTIFICATE----- MIIFaDCCBFC ... bml6YXRpb252YWxza ... lffygD5IymCSuuDim4qB/9bh7oi37heJ4ObpBIzroPUOthbG4gv/5blW3Dc= -----END CERTIFICATE----- ``` -------------------------------- ### Example: Create AWS key-secret vault (bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-aws-secret-manager-vault.htm Example command for creating an AWS vault with IAM Access Key authentication on a bundled k3s cluster. ```bash sudo ./edgecli vault create aws key-secret AWS-IAM \ --desc=AWS vault with IAM Access Key authentication. \ --region=eu-west-1 \ --endpointOverride=http://my-secret-vault.aws.com \ --accessKeyId=1234 \ --accessKey=abcd ``` -------------------------------- ### Show Edge CLI help for folder-upload with sudo Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AmazonRedshift/ta_redshift-create-shared-storage-conn.htm When the Edge site is installed on a bundled k3s cluster, prefix any Edge CLI command with sudo. This example shows the help command for folder-upload. ```bash sudo ./edgecli objects folder-upload -h ``` -------------------------------- ### Example excluding multiple hosts with wildcards Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/co_connecting-to-a-proxy-server.htm Example command excluding localhost, 127.0.0.1, and all IP addresses starting with 192.168* from the proxy. Use pipe (|) to separate hosts and asterisk (*) as wildcard. ```bash bin/lineage-harvester -Dhttps.proxyHost=proxy.example.com -Dhttps.proxyPort=443 -Dhttp.nonProxyHosts=localhost|127.0.0.1|192.168* ``` -------------------------------- ### Create AWS instance-profile vault example (managed Kubernetes) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-aws-secret-manager-vault.htm Example command for creating an AWS instance-profile vault on managed Kubernetes with a specific name, description, region, and endpoint override. ```bash ./edgecli vault create aws instance-profile AWS-Instance \ --desc=AWS vault with Instant Profile authentication \ --region=eu-west-1 \ --endpointOverride=http://my-secret-vault.aws.com ``` -------------------------------- ### Upload single file example with output Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AWSGlue/ta_aws-glue-create-shared-storage-conn.htm Example of uploading a single file to a shared folder, showing the command and its output. The file is uploaded with a custom key and TTL. ```bash ./edgecli objects file-upload --source /tmp/data-source-file-to-upload/a.txt \ --target shared-folder-2 \ --key rekeyed-a.txt \ --ttlSeconds 8000 ``` ```bash Uploaded 1 file: target=shared-folder-2 key=rekeyed-a.txt: size=14 ttlSeconds=8000 ``` -------------------------------- ### Install Edge site with terminal and file logging Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Command to run edgecli install with output teed to both the terminal and a timestamped log file. ```bash ./edgecli install 2>&1 | tee "edge-installer-$(date +"%Y-%m-%d_%H-%M-%S").log" ``` -------------------------------- ### Create Azure Key Vault with PFX certificate (managed Kubernetes) - example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-azure-key-vault.htm Example command for managed Kubernetes that creates a vault instance named 'Azure-service-principal-PFX' with a PFX certificate. It uses the default DNS suffix 'vault.azure.net' and example credentials. ```bash ./edgecli vault create azure sp-secret Azure-service-principal-PFX \ --desc Azure Key vault with service principal with PFX cert authentication. \ --dnsSuffix vault.azure.net \ --tenantId 165 \ --clientId AZ_22 \ --certPath ~/azurekey/vault/edge-site.pfx \ --certPassword AZ_PFX_password1 ``` -------------------------------- ### Service Principal ID authentication example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_azure-registry.htm Example command for installing an Edge site using an Azure Container Registry service principal. It uses the registry URL 'oci://edge.azurecr.io/myazurefolder', service principal ID 'azureEdge', and secret 'azureEdge12'. ```bash ./edgecli install \ --helm-url oci://edge.azurecr.io/myazurefolder \ --helm-user azureEdge \ --helm-pass azureEdge12 ``` -------------------------------- ### Check lineage harvester installation Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/LineageHarvestingApp/ta_install-lineage-harvesting-app.htm Run this command to verify that the lineage harvester is installed correctly. ```bash ./bin/lineage-harvester --help ``` -------------------------------- ### Example JSON key content for managed Kubernetes clusters Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ref_google-artifact-registry.htm When installing an Edge site on a managed Kubernetes cluster, you can provide the registry pass as the full JSON key content in a single line enclosed in single quotes. This example shows the JSON structure with empty fields. ```json {"type":"service_account","project_id":"","private_key_id":"","private_key":"","client_email":"","client_id":"","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_x509_cert_url":""} ``` -------------------------------- ### Example: Create AWS key-secret vault (managed Kubernetes) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-aws-secret-manager-vault.htm Example command for creating an AWS vault with IAM Access Key authentication on a managed Kubernetes cluster. ```bash ./edgecli vault create aws key-secret AWS-IAM \ --desc=AWS vault with IAM Access Key authentication. \ --region=eu-west-1 \ --endpointOverride=http://my-secret-vault.aws.com \ --accessKeyId=1234 \ --accessKey=abcd ``` -------------------------------- ### Create CyberArk Vault with mTLS (Bundled k3s) - Example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-cyberark.htm Example command for creating a CyberArk vault with mTLS authentication in a bundled k3s cluster. Uses placeholder values for demonstration. ```bash sudo ./edgecli vault create cyber tls Edge CyberArk Vault mTLS \ --desc CyberArk vault with mTLS authentication. \ --appId edge \ --url https://edge-cyberark-server.example.com \ --caPath ./certs/ca.crt \ --certPath ./certs/aimws.crt \ --keyPassword filePassword123 \ --keyPath ./certs/aimws-pkcs8.key ``` -------------------------------- ### Install Edge site with custom namespace Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Adds the -n flag to specify a custom namespace during installation. ```bash ./edgecli install -n ``` -------------------------------- ### Example base64 hash calculation Source: https://productresources.collibra.com/docs/collibra/latest/Content/Console/Infrastructure/DGCService/SecurityConfiguration/ta_configure-custom-certificate-for-sso-cdic.htm Example showing the result of calculating the base64 hash for the user 'apiUser' with password 'apiUserpassword'. ```bash echo 'apiUser:apiUserpassword' | base64 ``` -------------------------------- ### Example collibraSystemName mapping to System asset Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ta_dbt-core-source-config.htm Shows how to specify a project's collibraSystemName to stitch it to a System asset in Data Catalog. The example uses 'systemname1'. ```json { "collibraSystemNames":{ "projects":[ {"collibraSystemName":"systemname1"} ] }, } ``` -------------------------------- ### databaseSystemMapping configuration example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/ta_prepare-config-file.htm Example configuration for the databaseSystemMapping property, mapping databases DB2 and DB3 to their rightful systems SystemB and SystemC to resolve stitching issues. ```json { "id": "sql_dir", "type": "SqlDirectory", "path": "/tmp/sqldir", "dialect": "bigquery", "collibraSystemName": "SystemA", "database": "DB", "schema": "SCH", "databaseSystemMapping": { "DB2": "SystemB", "DB3": "SystemC" } } ``` -------------------------------- ### Verify Edge installation Source: https://productresources.collibra.com/docs/collibra/latest/Content/PracticalExamples/ta_example-edge-databricks.htm Check the status of the Kubernetes nodes and pods to confirm the installation. ```bash sudo /usr/local/bin/kubectl get nodes ``` ```bash sudo /usr/local/bin/kubectl get pods --all-namespaces ``` -------------------------------- ### File structure for custom lineage batch example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/CustomTechLin/ref_custom-lineage-json-file_example.htm Shows the required files for the custom lineage batch example: assets.json, lineage-1.json, lineage-2.json, and metadata.json. Source code files are optional. ```text __CUSTOM-LINEAGE__ ├── assets.json ├── lineage-1.json ├── lineage-2.json ├── metadata.json ``` -------------------------------- ### Start lineage harvester on Windows Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/LineageHarvestingApp/ta_install-lineage-harvesting-app.htm Run this command in the lineage harvester folder on Windows to start the harvester and create an empty configuration file in the config folder. ```batch .\bin\lineage-harvester.bat ``` -------------------------------- ### Install SELinux policy packages for Edge Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ref_edge-site-system-requirements.htm Install the container-selinux and selinux-policy-base packages required for SELinux-enabled Edge installations. ```bash yum install -y container-selinux selinux-policy-base ``` -------------------------------- ### Install Edge site with terminal logging Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Installs an Edge site on a managed Kubernetes cluster with terminal logging only. ```bash ./edgecli install ``` -------------------------------- ### Run Helm installer prerequisites script Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Runs the prerequisites script for the collibra-edge helm chart. Replace with your namespace. The --installer flag is required. ```bash sh collibra-edge-helm-chart/helm-install-prerequisites.sh --namespace --installer . ``` -------------------------------- ### Install Edge site with registry credentials and terminal logging Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Installs an Edge site using the Edge CLI, specifying a private Docker registry and credentials. The output is logged to both the terminal and a timestamped file. ```bash ./edgecli install \ --registry-url https://private-docker.registry.com \ --registry-user user1 \ --registry-pass pass12 \ 2>&1 | tee "edge-installer-$(date +"%Y-%m-%d_%H-%M-%S").log" ``` -------------------------------- ### Run the k3s installer script Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_install-edge-site.htm Runs the k3s installer script from the extracted directory. Use additional flags for proxy or private registry configuration. ```bash sudo sh install-master.sh -r registries.yaml ``` -------------------------------- ### filter example with jobIds and projectIds Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCloud/ta_dbt-cloud-source-config.htm Example showing how to filter which jobs and projects are downloaded. Only the job with ID 1234 and projects with IDs 98 and 5678 are processed. ```json { "filter": { "jobIds": [ 1234 ], "projectIds": [ 98, 5678 ] } } ``` -------------------------------- ### Create GCP IAM Role Vault Example (Bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-google-secret-manager-vault.htm Example command for bundled k3s with actual values: vault name GCP-IAM, description, and project ID IAM_145. ```bash sudo ./edgecli vault create gcp iam-role GCP-IAM \ --desc=GCP vault with IAM Role assigned to the Google Cloud Engine VM authentication \ --projectId=IAM_145 ``` -------------------------------- ### Example value for techlinHost property Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AmazonRedshift/ta_redshift-add-capability-cloud-storage.htm Example value for the techlinHost property, which is the URL of the Collibra Data Lineage service instance. ```text techlin-europe-west1.collibra.com ``` -------------------------------- ### Generated configuration file example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/LineageHarvestingApp/co_configuration-file.htm Example configuration file generated by the configuration file generator, showing properties for multiple data sources including ExternalDirectory, AzureDataFactory, dbt, and more. Replace the values to match your actual data source information. ```json { "general": { "catalog" : { "url" : "https://companydomain.collibra.com", "username" : "my-Collibra-username" }, "useCollibraSystemName" : false }, "sources" : [ { "id": "myAirflow", "type": "ExternalDirectory", "collibraSystemName": "None", "dirType" : "openlineage", "path" : "/opt/techlin/OL", "recursive" : false, "deleteRawMetadataAfterProcessing": false } { "id": "myAWSGlue", "type": "ExternalDirectory", "collibraSystemName": "None", "dirType" : "openlineage", "path" : "/opt/techlin/OL", "recursive" : false, "deleteRawMetadataAfterProcessing": false } { "id" : "adf_source", "type" : "AzureDataFactory", "tenantDomain": "tenant-domain", "loginFlow": { "type": "ServicePrincipal", "applicationId": "application-id" }, "subscriptionId" : "subscription-id", "resourceGroupName" : "resource-group-name", "factories" : ["factoryname1","factoryname2"], "deleteRawMetadataAfterProcessing": false } { "type": "dbt", "id": "mydbt", "tokenName": "mytokenname", "adminUrl":"https://cloud.getdbt.com/api/v2", "environmentIds":"[123456, 987654]", "metadataUrl":"https://metadata.cloud.getdbt.com/graphql", "deleteRawMetadataAfterProcessing": false } { "id" : "my_dbt_source", "type" : "ExternalDirectory", "dirType" : "dbt", "path" : "/opt/Collibra/techlin/dbt-core-files/", "recursive" : true, "deleteRawMetadataAfterProcessing" : false } { "id" : "datastage_source", "type" : "ExternalDirectory", "dirType" : "DATASTAGE", "path" : "/path/to/the/datastage/folder/", "mask" : "*", "recursive" : false, "deleteRawMetadataAfterProcessing": false } { "dialect" : "oracle", "id" : "informatica_source", "type" : "ExternalDirectory", ``` -------------------------------- ### Custom property example values Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AzureSQLServer/ta_azure-sql-server-add-capability-cloud-storage.htm Example values for custom properties: httpTimeout, linkedServerDatabaseMapping, linkedServerMapping, techlinHost, and techlinKey. ```text 15 ``` ```json {"LNKD1":"DB1","LNKD2":"DB2"} ``` ```json {"SRV1":"sys1","SRV2":"sys2"} ``` ```text techlin-europe-west1.collibra.com ``` ```text ``` -------------------------------- ### Create CyberArk Vault with mTLS (Managed Kubernetes) - Example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-cyberark.htm Example command for creating a CyberArk vault with mTLS authentication in a managed Kubernetes cluster. Uses placeholder values for demonstration. ```bash ./edgecli vault create cyber tls Edge CyberArk Vault mTLS \ --desc CyberArk vault with mTLS authentication. \ --appId edge \ --url https://edge-cyberark-server.example.com \ --caPath ./certs/ca.crt \ --certPath ./certs/aimws.crt \ --keyPassword filePassword123 \ --keyPath ./certs/aimws-pkcs8.key ``` -------------------------------- ### Output of file-upload example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/ApacheAirflow/ta_airflow-create-shared-storage-conn.htm Shows the expected output after uploading a single file with the file-upload command. ```text Uploaded 1 file: target=shared-folder-2 key=rekeyed-a.txt: size=14 ttlSeconds=8000 ``` -------------------------------- ### Example Assets File with nodes and props Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/CustomTechLin/ref_custom-lineage-json-file.htm Shows how to specify the highest levels of the hierarchy using the nodes property, with an example for GCS File System > GCS Bucket. The props property includes fullname and domain_id for stitching. ```json { "nodes": [ { "name": "GCS1", "type": "GCS File System" }, { "name": "GCS-B1", "type": "GCS Bucket" } ], "props": { "fullname": "", "domain_id": "" } } ``` -------------------------------- ### Service Account Key JSON Example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/GCS/Dataplex/ta_create-connection-gcp-dataplex-catalog.htm Example of the full content of a service account key JSON file, used for the Service Account authentication method when creating a GCP connection. Ensure the service account has the required permissions as defined in the prerequisites. ```json { "type": "service_account", "project_id": "PROJECT_ID", "private_key_id": "KEY_ID", "private_key": "-----BEGIN PRIVATE KEY-----\nPRIVATE_KEY\n-----END PRIVATE KEY-----\n", "client_email": "SERVICE_ACCOUNT_EMAIL", "client_id": "CLIENT_ID", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://accounts.google.com/o/oauth2/token", "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs", "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/SERVICE_ACCOUNT_EMAIL"} ``` -------------------------------- ### Vault create help command for bundled k3s installations Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Run this command in the Edge CLI on a bundled k3s installation to review helpful flags and required parameters for your vault integration. Replace with your authentication method, e.g., user-pass. ```bash sudo ./edgecli vault create hashicorp -h ``` -------------------------------- ### Example: Update HashiCorp Vault user-pass authentication (Bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Example command for updating a HashiCorp Vault instance with user-pass authentication in a bundled k3s environment. Uses the 'tls' name and includes --user, --pass, and --url flags. ```bash sudo ./edgecli vault update hashicorp tls "Hasicorp vault user-pass AuthN"\ --user my-edge-site \ --pass EdgePass123 \ --url https://hashicorp-vault.edge.collibra.dev:8210/ ``` -------------------------------- ### Start and check Fluentd service status Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AWSGlue/ta_aws-glue-set-up-fluentd-shared-storage.htm Command to start the Fluentd service and check its status. Used after installing the Fluentd package. ```bash sudo systemctl start fluentd.service; sudo systemctl status fluentd.service ``` -------------------------------- ### Reinstall Edge site with install-master.sh Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Reinstall using the new installer with the backup option. Include any additional installation scripts. The -r flag specifies the registries file, and -b specifies the backup path. ```bash sudo sh install-master.sh -r registries.yaml -b ``` -------------------------------- ### Example of custom priority class flags Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Shows how to use the --use-custom-priority-class flag with --set flags to configure custom priority classes for Edge platform, application, and job pods. The example uses critical-priority, high-priority, and low-priority as placeholders. ```bash --use-custom-priority-class --global.priorityClassName.platform critical-priority --global.priorityClassName.application high-priority --global.priorityClassName.job low-priority ``` -------------------------------- ### Get the installer path and set EDGE_INSTALLER_PATH Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_install-edge-site.htm Shows how to obtain the absolute path of the extracted installer and set the EDGE_INSTALLER_PATH environment variable. ```bash /path/to/installer/installer-111e8a59-b842-4f57-970c-32aa72000598 ``` ```bash export EDGE_INSTALLER_PATH=/path/to/installer/installer-111e8a59-b842-4f57-970c-32aa72000598 ``` -------------------------------- ### Get the extracted installer path Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Run pwd in the extracted installer directory to obtain the absolute path needed for the EDGE_INSTALLER_PATH environment variable. ```bash /path/to/installer/installer-111e8a59-b842-4f57-970c-32aa72000598 ``` -------------------------------- ### Example namespacePattern and nameTemplate with named capture groups Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/OpenLineage/ref_openlineage-custom-namespace.htm Example showing how to capture field values from the namespace. The namespacePattern captures 'database' and 'host', and the nameTemplate uses '{schema}.{table}'. ```json { "namespacePattern": "^mydb://(?P[^/]+)/(?P.+)$", "nameTemplate": "{schema}.{table}" } ``` -------------------------------- ### Create GCP IAM Role Vault Example (Managed Kubernetes) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_integrate-google-secret-manager-vault.htm Example command for managed Kubernetes with actual values: vault name GCP-IAM, description, and project ID IAM_145. ```bash ./edgecli vault create gcp iam-role GCP-IAM \ --desc=GCP vault with IAM Role assigned to the Google Cloud Engine VM authentication \ --projectId=IAM_145 ``` -------------------------------- ### GCP Service Account Key JSON Example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/GCS/GCSviaEdge/ta_add-connection-to-edge-site-gcs.htm Example of a service account key JSON file to paste into the 'GCP Service Account / Workload Identity Federation (WIF)' field. Ensure the service account has the required permissions as defined in the prerequisites. ```json { "type": "service_account", "project_id": "PROJECT_ID", "private_key_id": "KEY_ID", "private_key": "-----BEGIN PRIVATE KEY-----\nPRIVATE_KEY\n-----END PRIVATE KEY-----\n", "client_email": "SERVICE_ACCOUNT_EMAIL", "client_id": "CLIENT_ID", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://accounts.google.com/o/oauth2/token", "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs", "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/SERVICE_ACCOUNT_EMAIL" } ``` -------------------------------- ### Install k3s SELinux RPM for RHEL 9 Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ref_edge-site-system-requirements.htm Install the k3s-selinux RPM package for RHEL 9. This is required if you use RHEL 9 and want SELinux enabled. ```bash yum install -y https://github.com/k3s-io/k3s-selinux/releases/download/v1.6.latest.1/k3s-selinux-1.6-1.el9.noarch.rpm ``` -------------------------------- ### Install k3s SELinux RPM for RHEL 8 Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ref_edge-site-system-requirements.htm Install the k3s-selinux RPM package for RHEL 8. This is required if you use RHEL 8 and want SELinux enabled. ```bash yum install -y https://github.com/k3s-io/k3s-selinux/releases/download/v1.6.latest.1/k3s-selinux-1.6-1.el8.noarch.rpm ``` -------------------------------- ### Example: Update HashiCorp Vault user-pass authentication (Managed Kubernetes) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Example command for updating a HashiCorp Vault instance with user-pass authentication in a managed Kubernetes environment. Uses the 'tls' name and includes --user, --pass, and --url flags. ```bash ./edgecli vault update hashicorp tls "Hasicorp vault user-pass AuthN"\ --user my-edge-site \ --pass EdgePass123 \ --url https://hashicorp-vault.edge.collibra.dev:8210/ ``` -------------------------------- ### Recreate Linux disk mount for /var/lib/rancher/k3s Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Commands to recreate the Linux disk mount for the /var/lib/rancher/k3s directory. This is the default installation path; if not created as a separate mount point, the installation will use 50 GB of disk space from /var or root. ```bash mkdir -p /var/lib/rancher/k3s ``` ```bash mount -a ``` ```bash rm -rf /var/lib/rancher/k3s/* ``` -------------------------------- ### Workspace filter configuration example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/PowerBI/co_power-bi-workspaces.htm Example JSON configuration for workspace filters. The first matching filter takes precedence, so the wildcard '*' in the first filter causes all workspaces to be ingested into DOMAIN_A, and the second filter for 'my_workspace' is ignored. ```json [ { "domainId": "DOMAIN_A", "workspaceNames": [ "*" ] }, { "domainId": "DOMAIN_B", "workspaceNames": [ "my_workspace" ] } ] ``` -------------------------------- ### Example: Update HashiCorp Vault TLS configuration (bundled k3s) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Example command for updating a HashiCorp Vault TLS configuration in a bundled k3s cluster. Uses a vault name 'tls-vault-auth', a certificate path, a key path, and a URL. ```bash sudo ./edgecli vault update hashicorp tls "tls-vault-auth"/ --authName "tls-vault-auth" \ --certPath "~/hashicorp/vault/edge-site.crt" \ --keyPath "~/hashicorp/vault/edge-site.key" \ --url "https://hashicorp-vault.edge.collibra/" ``` -------------------------------- ### Vault create help command for managed Kubernetes installations Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Run this command in the Edge CLI on a managed Kubernetes installation to review helpful flags and required parameters for your vault integration. Replace with your authentication method, e.g., user-pass. ```bash ./edgecli vault create hashicorp -h ``` -------------------------------- ### Example lineage-harvester.conf for dbt Core Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/ta_prepare-config-file.htm Example configuration file for the lineage harvester with a dbt Core source. It sets the Data Catalog connection, disables useCollibraSystemName, and specifies the external directory path with recursive scanning and deleteRawMetadataAfterProcessing set to false. ```json { "general" : { "catalog" : { "url" : "https://.collibra.com", "username" : "" }, "useCollibraSystemName" : false }, "sources" : [ { "id" : "my_dbt_source", "collibraSystemName" : "", "type" : "ExternalDirectory", "dirType" : "dbt", "path" : "/opt/Collibra/techlin/dbt-core-files/", "recursive" : true, "deleteRawMetadataAfterProcessing" : false } ] } ``` -------------------------------- ### Kubernetes RBAC Role and RoleBinding for Edge namespace Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ref_edge-site-system-requirements.htm Example Kubernetes RBAC configuration for the collibra-edge namespace. The Role grants all permissions on all resources, and the RoleBinding binds it to a user. The user must be replaced with the actual username performing the installation. ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: edge-namespace-role namespace: collibra-edge rules: - apiGroups: ["*"] resources: ["*"] verbs: ["*"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: edge-namespace-rb namespace: collibra-edge subjects: - kind: User name: username> # The user that will perform the installation namespace: collibra-edge roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: edge-namespace-role ``` -------------------------------- ### Example materializedMapping to view Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ta_dbt-core-source-config.htm Shows how to map the ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES materialization to a view. ```json "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } ``` -------------------------------- ### Run the CLI binary to confirm it works Source: https://productresources.collibra.com/docs/collibra/latest/Content/CLI/ta_set-up-cli.htm Commands to execute the CLI binary without arguments, which should display a help message. ```Windows .\collibra ``` ```Linux ./collibra ``` ```Mac ./collibra ``` -------------------------------- ### Get Edge site diagnostics Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSiteManagement/co_edge-cli.htm Run this command to collect diagnostics from your Edge site and provide the results to Collibra Support. If your Edge site is installed on a dedicated cluster without a custom namespace, you can omit the -n part. ```bash ./edgecli diagnostics -n -d ``` -------------------------------- ### Extract Edge site installer Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Extract the downloaded installer to an empty folder. The installer is a single-use installer for your Edge site. ```bash tar -xf installer-.tgz ``` -------------------------------- ### Matillion source ID configuration example with collibraSystemName Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/TechlinViaCLI/InstallationAndConfiguration/LineageHarvestingApp/ta_source-id-config-files.htm Example JSON configuration for a Matillion source ID file. It shows how to map found_dbname and found_hostname connection strings to Data Catalog assets, including using wildcards and specifying collibraSystemName to handle databases with the same name. ```json { "found_dbname=dbtest;found_hostname=test": { "dbname": "Customers", "collibraSystemName": "Customers-Europe" }, "found_dbname=testsid;found_hostname=*": { "dbname": "Customers", "schema": "oracle-schema-name", "collibraSystemName": "Customers-USA" } } ``` -------------------------------- ### IRSA Trust Relationship Policy for Edge Service Account Source: https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/S3/S3viaEdge/ta_prep-S3-edge.htm Example trust relationship policy allowing the Edge service account to assume the IRSA role via web identity federation. Replace '' and '' with your OIDC provider values. Assumes Edge is installed in the 'collibra-edge' namespace; adjust as needed. ```json { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "Federated": "" }, "Action": "sts:AssumeRoleWithWebIdentity", "Condition": { "StringEquals": { ":aud": "sts.amazonaws.com" }, "StringLike": { ":sub": "system:serviceaccount:collibra-edge:*" } } }] } ``` -------------------------------- ### Assets JSON file for custom lineage batch example Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/CustomTechLin/ref_custom-lineage-json-file_example.htm Defines the assets to include in the technical lineage, with nodes, parent, leaf, and props. The example includes a GCS file and a Snowflake column. ```json [{ "nodes": [{ "name": "gcs", "type": "GCS File System" }, { "name": "catingestiontest", "type": "GCS Bucket" }, { "name": "/", "type": "Directory" }, { "name": "ingestion-test", "type": "Directory" }], "parent": { "name": "ingestion copy", "type": "Directory" }, "leaf": { "name": "mytest.csv", "type": "File" }, "props": { "fullname": "f13bf705-13a4-44c9-843e-f341feccfb6e > catingestiontest/ingestion-test/ingestion copy/mytest.csv/1611609340099809", "domain_id": "fea1b0b0-705f-4e0d-b5eb-1f21132cc718" } }, { "nodes": [{ "name": "snowflake", "type": "System" }, { "name": "DB1", "type": "Database" }, { "name": "PUBLIC", "type": "Schema" }], "parent": { "name": "T1", "type": "Table" }, "leaf": { "name": "col3", "type": "Column" } }] ``` -------------------------------- ### Example metadata.json file Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/CustomTechLin/ref_custom-lineage-json-file.htm Example metadata file for Databricks technical lineage. The version must be 3 for batch-file instructions. The asset_types property maps asset type names to UUIDs. ```json { "version": 3, "application_name": "databricks", "asset_types":{ "Column":{"uuid": "00000000-0000-0000-0000-000000031008"}, "Table":{"uuid": "00000000-0000-0000-0000-000000031007"}, "Database":{"uuid": "00000000-0000-0000-0000-000000031006"}, "Schema":{"uuid": "00000000-0000-0000-0001-000400000002"} } } ``` -------------------------------- ### Install Edge site with backup file and file logging Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Run this command to reinstall an Edge site using a backup file while saving output to both the terminal and a log file. The log file is saved in the current directory with the format edge-installer-$(date +"%Y-%m-%d_%H-%M-%S").log. Do not exclude -b . ```bash ./edgecli install -b 2>&1 | tee "edge-installer-$(date +"%Y-%m-%d_%H-%M-%S").log" ``` -------------------------------- ### DGC service address example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Console/Infrastructure/JobserverService/CollibraToJS/ta_configure-js-to-cloud-communication-platform-config.htm Example of the loopback address for the DGC service, followed by /reversehttp/. Do not use the scheme. Example: localhost:4400/reversehttp/Jobserver-1 ```text localhost:4400/reversehttp/Jobserver-1 ``` -------------------------------- ### Trusted server CA certificate example Source: https://productresources.collibra.com/docs/collibra/latest/Content/Console/Infrastructure/JobserverService/CollibraToJS/ta_configure-js-to-cloud-communication-platform-config.htm Example of a PEM certificate containing the public key of the Jobserver. This is the content of the file cert.pem from the keystore creation example. ```text -----BEGIN CERTIFICATE----- MIICqDCCAZACCQCcy3Oq51c5YzANBgkqhkiG9w0BAQsF ADAWMRQwEgYDVQQDDAtq b2JzZXJ2ZXIt... -----END CERTIFICATE----- ``` -------------------------------- ### Extract the Edge installer archive Source: https://productresources.collibra.com/docs/collibra/latest/Content/PracticalExamples/ta_example-edge-databricks.htm Extract the downloaded Edge installer tarball. ```bash tar -xf .tgz ``` -------------------------------- ### Install Edge site with backup file (terminal logging) Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_reinstall-edge-site.htm Run this command to reinstall an Edge site using a backup file. Output is only saved to the terminal. ```bash ./edgecli install -b ``` -------------------------------- ### Edit fast_context_jvm.conf with vi Source: https://productresources.collibra.com/docs/collibra/latest/Content/Console/Infrastructure/JobserverService/CollibraToJS/ta_create-keystore-platform-config.htm Example command to edit the fast_context_jvm.conf file using vi. ```bash vi /opt/collibra/spark-jobserver/conf/fast_context_jvm.conf ``` -------------------------------- ### Help command output for user-pass authentication Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSecurity/ta_manage-hashicorp-vault.htm Example help command for username and password authentication, showing the usage and available flags for the edgecli vault create hashicorp user-pass command. ```bash ./edgecli vault create hashicorp user-pass -h create HashiCorp secret vault with user-pass authN type Usage: edgecli vault create hashicorp user-pass [flags] Flags: --caPath string path to CA certificate file [optional] --vaultNamespace string optional - A specific non default namespace in vault --pass string password in user-pass auth --user string username in user-pass auth Global Flags: --desc string description for the vault [optional] -h, --help --name string name for the vault [optional] --url string the url to reach for the vault ``` -------------------------------- ### Example namespacePattern field Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/OpenLineage/ref_openlineage-custom-namespace.htm Example of a namespacePattern field using a named capture group 'host'. ```json "namespacePattern": "^snowflake://(?P.+)$" ``` -------------------------------- ### Get help for folder-upload command Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/AWSGlue/ta_aws-glue-create-shared-storage-conn.htm Displays help information for the folder-upload command, including its parameters and usage. ```bash ./edgecli objects folder-upload -h ``` -------------------------------- ### Example configuration for filters section Source: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/Tableau/ta_tableau-source-config.htm Shows how to specify sites and projects with their domain IDs in the 'filters' section. The 'site_name' and 'project_name' keys map to domain IDs. Spaces around '>' are required and values are case-sensitive. ```json { "filters":{ "sites":{ "Training":"ca60b822-781b-4b3a-b44d-f65bd107ff92" }, "projects":{ "Testing > Databricks":"e8f4e4a8-4062-4a33-9b44-3ce3e18e4e22", "Product Demo > Customer Insights":"a305e6f7-7a49-49aa-aa85-41b1e689121b" } } } ``` -------------------------------- ### Extract the Edge site installer TGZ archive Source: https://productresources.collibra.com/docs/collibra/latest/Content/Edge/EdgeSitesInstallation/ta_configure-forward-proxy.htm Use this command to extract the downloaded Edge site installer TGZ archive on the server where you want to install the Edge site. Replace with your actual site ID. ```bash tar -xf -installer.tgz ```