GantryCD
Integrations
GantryCD plugs into the systems you already run — your Git platform, your cloud, your compute, your identity provider — through five integration surfaces. Each surface has a small set of implementations, and each implementation has its own page in this section.
| Surface | Implementations today | You use it to |
|---|---|---|
| Source control | GitHub App | Receive webhooks, mint clone credentials, project pull requests. |
| Cloud providers | AWS, GCP | Give a run short-lived access to your cloud. |
| Notifications | Slack, Webhook | Announce deployment executions to your chat/alerting systems. |
| Runner groups | Local, Docker, Kubernetes, GitHub Actions | Choose where OpenTofu actually executes. |
| Single sign-on | GitHub, Google, OIDC | Let people sign in and map them to access. |
| Secret encryption | AES-256, AWS KMS | Encrypt every secret GantryCD stores at rest. |
One pattern, five surfaces
Every surface follows the same shape, so once you’ve configured one you can read the rest by analogy:
interface ──implemented by──▶ a provider ──registered in──▶ cmd/backend
(one method set) (a package) (one line)The core of GantryCD — the run state machine, the HTTP protocol, persistence — is generic and never changes when you add or swap a provider. Registries reject duplicate keys at construction, so a wiring mistake is a boot-time crash rather than a runtime surprise.
Operators vs. contributors
- Configuring an integration (picking a provider, supplying credentials): each implementation page has a Configure section with the exact settings.
- Adding a new implementation (a new cloud, a new IdP, a new runner type): the pattern and the seams are in Extending GantryCD, and each surface links to its implementation-level reference.