Chapter 09

Integrations

Integrations connect Vyazen to external services — source-control managers (for repositories) and OAuth providers (for sign-in). Setting these up is usually an admin task; this page is the reference for what each one does and how it's managed.

~2 min read7 sections

Overview

There are two kinds of integration:

Source-control managers (SCM) — GitHub, GitLab, and Bitbucket. These let you connect repositories so Vyazen can clone and index them, and so the agent can push branches and open pull requests.
OAuth providers — used for signing in to Vyazen (e.g., Google).

GitHub (GitHub App)

If your instance uses the GitHub App, an admin installs the app into a GitHub account or organization and selects which repositories it may access. Once installed:

The selected repositories become available to connect in Vyazen.
The agent can push branches and open pull requests back to those repos.

note

A repository won't appear in Vyazen until the GitHub App has been granted access to it in GitHub. If a repo is missing, an admin may need to expand the app's access.

GitLab

Connect GitLab using an access token with read access to the target group or repository. An admin configures the token as an integration; users then connect repos and branches from that GitLab account.

Bitbucket / Bitbucket Cloud

Connect Bitbucket using credentials configured as an integration by an admin. Once configured, users connect repos and branches from that Bitbucket account.

OAuth providers — such as Google — are used to sign in to Vyazen. An admin enables a provider; users then see a "Sign in with …" button on the sign-in page. This is separate from source-control integrations.

Webhooks

Source-control integrations rely on webhooks so Vyazen reacts to changes upstream — for example, syncing a repository when it's pushed to, which triggers re-indexing. These are configured as part of the integration; you usually don't manage them manually.

Managing and removing integrations

From the integrations page (an admin area), you can review configured providers and remove one when it's no longer needed. Removing an integration disconnects the repositories that depended on it.