Run Domo Pipeline using the Metadata CLI

In this section, we provide guides and references to use the Domo Pipeline connector.

Configure and schedule Domo Pipeline metadata and profiler workflows from the OpenMetadata UI:

To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment.


For metadata ingestion, kindly make sure add alteast data scopes to the clientId provided. Question related to scopes, click here.

To run the Domo Pipeline ingestion, you will need to install:

pip3 install "openmetadata-ingestion[domo]"

All connectors are defined as JSON Schemas. Here you can find the structure to create a connection to Airbyte.

In order to create and run a Metadata Ingestion workflow, we will follow the steps to create a YAML configuration able to connect to the source, process the Entities if needed, and reach the OpenMetadata server.

The workflow is modeled around the following JSON Schema

This is a sample config for Domo-Pipeline:

  type: domopipeline
  serviceName: domopipeline_source
      type: DomoPipeline
      clientId: clientid
      secretToken: secret-token
      accessToken: access-token
      sandboxDomain: https://<api_domo>
      type: PipelineMetadata
      # pipelineFilterPattern:
      #   includes:
      #     - pipeline1
      #     - pipeline2
      #   excludes:
      #     - pipeline3
      #     - pipeline4
  type: metadata-rest
  config: {}
  # loggerLevel: DEBUG  # DEBUG, INFO, WARN or ERROR
    hostPort: <OpenMetadata host and port>
    authProvider: <OpenMetadata auth provider>

Source Configuration - Service Connection

  • Client ID: Client ID to Connect to DOMO Pipeline.
  • Secret Token: Secret Token to Connect DOMO Pipeline.
  • Access Token: Access to Connect to DOMO Pipeline.
  • API Host: API Host to Connect to DOMO Pipeline instance.
  • SandBox Domain: Connect to SandBox Domain.

Source Configuration - Source Config

The sourceConfig is defined here:

  • dbServiceNames: Database Service Name for the creation of lineage, if the source supports it.
  • pipelineFilterPattern and chartFilterPattern: Note that the pipelineFilterPattern and chartFilterPattern both support regex as include or exclude. E.g.,
    - users
    - type_test

Sink Configuration

To send the metadata to OpenMetadata, it needs to be specified as type: metadata-rest.

Workflow Configuration

The main property here is the openMetadataServerConfig, where you can define the host and security provider of your OpenMetadata installation.

For a simple, local installation using our docker containers, this looks like:

    hostPort: 'http://localhost:8585/api'
    authProvider: openmetadata
      jwtToken: '{bot_jwt_token}'

We support different security providers. You can find their definitions here. You can find the different implementation of the ingestion below.

chevron_rightConfigure SSO in the Ingestion Workflows

First, we will need to save the YAML file. Afterward, and with all requirements installed, we can run:

metadata ingest -c <path-to-yaml>

Note that from connector to connector, this recipe will always be the same. By updating the YAML configuration, you will be able to extract metadata from different sources.

Still have questions?

You can take a look at our Q&A or reach out to us in Slack

Was this page helpful?

editSuggest edits