---
title: "CI Drift Gate for Glue"
slug: "ci-drift-gate"
type: recipe
locale: en-US
canonical: "https://www.coremodels.io/recipe/glue/ci-drift-gate"
updatedAt: "2026-08-27T01:42:16+03:00"
---

# CI Drift Gate for Glue

Catch crawler re-inference before it breaks something downstream.

Import your Glue catalog export, record the first audit, and wire the audit gate into your CI pipeline: CI runs aws glue get-tables with your repo's usual AWS OIDC/credentials step (AWS credentials go to AWS, never to CoreModels), calls the API-key audit surface (v1/{projectId}/integrations/glue/audit), and fails the build when data.errorCount > 0. A crawler that re-infers a numeric column as string becomes a failed build with the exact table and column named, not an incident discovered next Monday. An SVG status badge reports the latest recorded run.

## Articles

- [Automating Glue Drift: The Gate, the Trail, and the Heartbeat](https://www.coremodels.io/connector/glue/t4-automation)
- [After the Import: What a Governed Glue Catalog Changes Day to Day](https://www.coremodels.io/connector/glue/h2-outcomes)