Integrate Datafold with your custom orchestration using the Datafold SDK and REST API.
datafold-sdk
from the available options, complete configuration with the following information:
Field Name | Description |
---|---|
Repository | Select the repository that generates the webhooks and where pull / merge requests will be raised. |
Data Connection | Select the data connection where the code that is changed in the repository will run. |
Name | An identifier used in Datafold to identify this CI configuration. |
Files to ignore | If defined, the files matching the pattern will be ignored in the PRs. The pattern uses the syntax of .gitignore. Excluded files can be re-included by using the negation; re-included files can be later re-excluded again to narrow down the filter. |
Mark the CI check as failed on errors | If the checkbox is disabled, the errors in the CI runs will be reported back to GitHub/GitLab as successes, to keep the check “green” and not block the PR/MR. By default (enabled), the errors are reported as failures and may prevent PR/MRs from being merged. |
Require the datafold label to start CI | When this is selected, the Datafold CI process will only run when the ‘datafold’ label has been applied. This label needs to be created manually in GitHub or GitLab and the title or name must match ‘datafold’ exactly. |
Sampling tolerance | The tolerance to apply in sampling for all data diffs. |
Sampling confidence | The confidence to apply when sampling. |
Sampling Threshold | Sampling will be disabled automatically if tables are smaller than specified threshold. If unspecified, default values will be used depending on the Data Connection type. |
ci_config_id
, pr_num
, and diffs_file
with the appropriate values for your CI configuration ID, pull request number, and the path to your diffs JSON
file.
JSON
file should define the production and pull request tables to compare, along with any primary keys and columns to include or exclude in the comparison.