Skip to content

External Catalogs

Audience: Application Admins

Content Summary: Immuta allows you to integrate external catalogs from different tools, such as Collibra, Apache Atlas, and Waterline Data. These tools and Alteryx, BigID, and Podium can all be configured in the Catalogs section of the Application Settings page.

However, if you have contacted the Immuta Support team and they have instructed you to add advanced configuration options, these options can be managed in the Advanced Configuration section of the Application Settings page. This page outlines configuration and examples for Collibra integration, Apache Atlas integration, and Waterline Data integration.

For information about governing data from external catalogs, navigate to the Tags Guide.

Immuta can integrate a variety of data sources for external catalogs. For additional information contact an Immuta Support Professional.

Configuring Collibra Integration

In your config.yml file, include the following under plugins. If you have preexisting plugins in your configuration, simply append collibra to the plugins set.

Parameters:

  • requestOptions:
    • uri: Collibra's integration endpoint.
  • authentication:
    • username: username for the integration.
    • password: password for the integration.
  • assetMapping: an array of data source nodes.
    • dataSource: table name to import.
    • columns: columns to import.
    • columnsAreSource: when true, indicates that the specified columns are the source asset, and the data source is the target. Set to false to invert this relationship.

Example:

# config.yml
# ...
  plugins:
    collibra:
      requestOptions:
        uri: 'https://techintegrations.collibra.com'
      authentication:
        username: '<USERNAME>'
        password: '<PASSWORD>'
      assetMapping:
      - dataSource: '<TABLE_1>'
        columns: '<COLUMN> '
        columnsAreSource: true
      - dataSource: '<TABLE_2>'
        columns: '<COLUMN>'
        columnsAreSource: true
# ...

Configuring Apache Atlas Integration

In your config.yml file, include the following under plugins. If you have preexisting plugins in your configuration, simply append atlas to the plugins set.

Parameters:

  • requestOptions:
    • uri: Atlas's API endpoint, including the authentication details and the port, conforming to the following format: https://<USERNAME>:<PASSWORD>@<ATLAS_API_ENDPOINT>:<PORT>.

Example:

# config.yml
# ...
  plugins:
    atlas:
      requestOptions:
        uri: 'https://admin:secret@path.to.atlas.api:21000'

Configuring Waterline Data Integration

In your config.yml file, include the following under plugins. If you have preexisting plugins in your configuration, simply append waterline to the plugins set.

Parameters:

  • requestOptions:
    • uri: Waterline Data's integration endpoint.
  • authentication:
    • username: username for the integration.
    • password: password for the integration.
  • domainMapping:
    • Built-in_Tags: built-in tag to import.
  • tagStates: an array of tag states to accept from Waterline Data.

Example:

# config.yml
# ...
  plugins:
    waterline:
      requestOptions:
        uri: 'https:/path.to.waterline.integration.com:8082'
      authentication:
        username: '<USERNAME>'
        password: '<PASSWORD>'
      domainMapping:
        Built-in_Tags: 'my_org'
      tagStates:
      - ACCEPTED
      - SUGGESTED