GitLab

Uses: Catalog Kong Gateway

Prerequisites

You need the Owner GitLab role to authorize the integration. This is required for event ingestion.
Only GitLab.com subscriptions are supported at this time.
If you’re using a self-hosted GitLab instance, it must be accessible from the public internet or is otherwise reachable by Konnect. For more information, review the Konnect hostnames documentation

To use the GitLab integration in a self-hosted environment:

Create a group-owned application in your GitLab instance. This is required to enable OAuth access for your organization.
- Set the redirect URI in GitLab to https://cloud.konghq.com/$KONNECT_REGION/service-catalog/integrations/gitlab
- Make sure the application has the api scope.
In the Konnect UI, navigate to the GitLab integration.
In the GitLab API Base URL field, enter the full URL to your GitLab API, ending in /api/v4.
For example: https://gitlab.example.com/api/v4
Fill out the authorization fields using the values from your GitLab OAuth application:
- Application ID: The Application ID from your GitLab app
- Application Secret: The secret associated with your GitLab app
- Token Endpoint: https://$GITLAB_HOST/oauth/token
- Authorization Endpoint: https://$GITLAB_HOST/oauth/authorize
Click Authorize to complete the connection.

Entity	Description
Projects	Organizes all the data for a specific development project that relates to a Catalog Classic service.

This integration supports events.

You can view the following event types for linked projects from the Konnect UI: