Prerequisites:
- This feature is available with the Paradime Bolt plan.
- Your API keys must have either Bolt Schedules Admin or Bolt Schedules Metadata Viewer capabilities.
These examples authenticate with an account API key (
api_secret="prdm_cmp_..." plus workspace_uid), which requires paradime-io 6.0.0 or later. Legacy workspace API keys (api_key + api_secret) are still supported. See Getting Started.Trigger Lineage Diff report and wait until report is returned
Triggers a lineage diff report for the specified parameters and waits until generation is completed.int
required
The ID of the completed Turbo CI bolt run.
int
required
The number of the pull request.
str
required
The email of the user triggering the report (pull request author).
List[str]
required
A list of file paths that have changed in the pull request.
int
default:"3600"
Maximum time in seconds to wait for the report to be available.
Report
The lineage diff report.
Trigger Lineage Diff report
Triggers a lineage diff report for the specified parameters and returns the report UUID immediately, without waiting for generation to complete.int
required
The ID of the completed Turbo CI bolt run.
int
required
The number of the pull request.
str
required
The email of the user triggering the report (pull request author).
List[str]
required
A list of file paths that have changed in the pull request.
str
The UUID of the triggered lineage diff report.
Fetch Lineage Diff report
Fetches a lineage diff report by its UUID.str
required
The UUID of the lineage diff report.
Report
The lineage diff report.
Report object details
Thereport object provides several options that can be selected with the following attributes:
message: A string containing details of the report status.status: Indicates the status of the operation or request.url: A string representing a URL to the Bolt schedule compiling the two git branches.uuid: A unique identifier for the report.result_json: Contains the result in JSON format.result_markdown: Provides the result in Markdown format.