Once you’ve registered your critical data assets, and published contracts for those assets, it’s time to configure Gable’s CI/CD to prevent changes in product repositories that would violate a data asset’s contract. Gable provides Github Actions to easily configure contract violation checks in your workflows. Don’t see your CI/CD provider? You can always use the gable CLI to achieve the same outcome. Reach out to our support team for guidance, and to let us know we should start working on a native implementation. Below is an example comment left by Gable’s Github Action when it detected that a database migration dropped a column that was part of a data contractDocumentation Index
Fetch the complete documentation index at: https://docs.gable.ai/llms.txt
Use this file to discover all available pages before exploring further.
