REST API Hybrid Runner

• Requirements
• Metadata Ingestion
• Troubleshooting

​

Requirements

​

Configure the OpenAPI Schema URL

1. Generate an OpenAPI specification for the service.
2. In the REST service connection form, select OpenAPI Schema URL.
3. In OpenAPI Schema URL, enter an HTTP or HTTPS URL that is reachable from the configured ingestion runner and points directly to the schema file.
4. Optional: In Token, enter a bearer token if the URL requires authentication.

​

Supported Formats

• JSON (.json)
• YAML (.yaml or .yml)

​

Configure an S3-Hosted Schema

1. In the REST service connection form, select OpenAPI Schema S3 URL when the OpenAPI schema is stored in Amazon S3, including when the object is private.
2. In OpenAPI Schema S3 URL, enter the HTTPS object URL in the following format:
   https://<bucket>.s3.<region>.amazonaws.com/<object-key>
   
3. In AWS Region, enter the bucket’s Amazon Web Services (AWS) Region.
4. In the AWS credential configuration, choose the credential method used by the ingestion runner:
   • Enable AWS Identity and Access Management (IAM) authentication with IAM Auth to use the runner’s default AWS credential provider chain, including a workload or instance role.
   • Configure an access key and secret. Include the session token when using temporary credentials.
   • Select a named AWS profile that is available in the runner environment.
5. Optional: In assumeRoleArn, enter the target role Amazon Resource Name (ARN) after selecting a source credential method. The target role’s trust policy must allow the source principal. For cross-account role assumption, the source principal’s identity policy must also allow sts:AssumeRole. For same-account role assumption, an identity policy is required unless the trust policy grants the source principal permission directly.

​

Configure S3 Access for the Hybrid Runner

1. Grant the effective ingestion principal s3:GetObject on the exact schema object through an IAM identity policy.
2. Add a bucket policy granting the same principal s3:GetObject on the exact schema object:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowHybridRunnerOpenAPISchemaRead",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::<account-id>:role/<effective-ingestion-role>"
      },
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::<bucket>/<object-key>"
    }
  ]
}

​

Metadata Ingestion

​

Step 1: Add New Service

1. In the left navigation, click Connections.
2. On the Connections page, click Add New Service.

​

Step 2: Select a Service and Connector

​

Step 3: Add Service Name and Description

• Enter a unique, descriptive Service Name. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other REST services you are ingesting metadata from.
• Optional: Enter a Description for the service.

​

Step 4: Configure Connection Options

​

Select Ingestion Runner

​

Enter Connection Details

• OpenAPI Schema URL: HTTP or HTTPS URL pointing directly to your OpenAPI schema file (for example https://petstore3.swagger.io/api/v3/openapi.json).
• OpenAPI Schema S3 URL: HTTPS S3 object URL when the schema is stored in S3. Configure AWS Region and credentials alongside it.
• Token (optional): Bearer token if the schema URL requires authentication.

password: secret:/my/database/password

​

Test Connection

​

Step 5: Configure Ingestion Options

​

How Filter Patterns Work

• Include: Add one or more comma-separated regular expressions. Collate ingests only assets whose names match at least one expression. Leave blank to include all assets.
• Exclude: Add one or more comma-separated regular expressions. Collate skips any asset whose name matches an expression. Leave blank to exclude nothing.

• contains: matches any name containing the value. For example, sales matches my_sales_data and sales_2024.
• starts with: matches names beginning with the value. For example, prod_ matches prod_db and prod_schema.
• ends with: matches names ending with the value. For example, _raw matches events_raw and logs_raw.
• is exactly: matches the exact name only. For example, analytics matches only analytics.
• matches regex: matches names using a regular expression. For example, ^prod_.*_v\d+$ matches prod_events_v1.

• API Collection: Controls which API collections (groups of endpoints defined in an OpenAPI specification) Collate ingests from the source.

• Scan Mode: You can choose between the following scan modes:
  • Scan all: Ingests every asset of that type the connector can access. This is the default.
  • Only specific: Enables include rules so only assets matching at least one rule are ingested.
• Exclude system toggle: Use this toggle to automatically filter out system-reserved names defined by the connector — for example, Exclude system databases for the Databases section.
• Always exclude: Add permanent exclusion rules (shown in red). Assets matching these rules are never ingested, regardless of include rules.
• Preview: Shows a real-time summary of what will be in scope based on your current rules.
• Include rules (available only in Only specific mode): Click + Add to define a rule. Added rules appear as chips; an asset is included if it matches any rule.

​

Step 6: Create & Deploy

​

Configure Metadata Agent and Schedule Ingestion

1. In the left navigation, click Connections and select your service.
2. Click the Agents tab.
3. Click Add Agent and select Metadata from the dropdown. For some services, the dropdown is not available and clicking Add Agent takes you directly to the agent configuration page.
4. On the Configure Ingestion page, do the following and click Next.
   • Name this Ingestion: Enter a unique recognizable name for this ingestion pipeline.
   • Filter Patterns: Apply include or exclude rules to scope which API collections and endpoints this agent ingests. These follow the same filter options described in Step 5.
   • Scope & Behaviour: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs:

     Toggle	Default	Description
     Mark Deleted API Collections	On	Soft-delete API collections in Collate when they are removed from the source. Associated entities like lineage are also deleted.
     Override Metadata	Off	When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. When off, Collate only updates fields that have no existing value.
     Enable Debug Log	Off	Sets the ingestion log level to DEBUG. Useful for troubleshooting.

     
5. On the Schedule Interval page, set when the agent runs:
   • Schedule: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
   • On-Demand: No automatic schedule; trigger the agent manually when needed.
   
6. Click Add to deploy the agent.

​

Troubleshooting