Query, Visualize, and Share live GitLab Data in Redash
Redash is a collaboration tool that lets you query, visualize, and share your data. When paired with CData Connect AI, Redash gets access to live GitLab data. This article demonstrates how to connect to GitLab using Connect AI and work with live GitLab data in Redash.
CData Connect AI provides a pure SQL Server interface for GitLab, allowing you to query data from GitLab without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to GitLab, leveraging server-side processing to return the requested GitLab data quickly.
Configure GitLab Connectivity for Redash
Connectivity to GitLab from Redash is made possible through CData Connect AI. To work with GitLab data in Redash, we start by creating and configuring a GitLab connection.
- Log into Connect AI, click Sources, and then click Add Connection
- Select "GitLab" from the Add Connection panel
-
Enter the necessary authentication properties to connect to GitLab.
To connect to GitLab, use either OAuth or a personal access token:
Using OAuth
Register an OAuth application in GitLab under Edit Profile > Applications (or group Settings > Applications). Set the Redirect URI to https://oauth.cdata.com/oauth/. Note the Application ID (OAuth Client Id) and Secret (shown once). Then set:
- OAuth Client Id: The Application ID from your GitLab OAuth application.
- OAuth Client Secret: The Secret from your GitLab OAuth application.
Click Sign In to complete OAuth authentication.
Using a Personal Access Token
In GitLab, navigate to Edit Profile > Access Tokens > Add new token. Select the required scopes (such as api, read_api, read_user, read_repository) and set an expiration date. Copy the token immediately (shown only once). Then set:
- API Key: The personal access token from your GitLab account.
- Click Save & Test
-
Navigate to the Permissions tab in the Add GitLab Connection page and update the User-based permissions.
Add a Personal Access Token
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
- Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
With the connection configured and a PAT generated, you are ready to connect to GitLab data from Redash.
Connect to GitLab from Redash using Connect AI
To establish a connection from Redash to CData Connect AI using the Virtual SQL Server, follow these steps:
- Log into Redash.
- Click the settings widget on the top right.
- Click New Data Source.
- Select Microsoft SQL Server as the Data Source Type.
-
On the configuration tab, set the following properties:
- Database Name: enter the Connection Name of the CData Connect AI data source you want to connect to (for example, Salesforce1).
- Server: enter the virtual SQL Server host name (tds.cdata.com)
- User: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
- Password: enter the PAT you generated on the Settings page.
- Port: enter 14333
- Click Create.
- Click Test Connection to ensure that the connection is configured properly.
You can now work with live GitLab data in Redash.
Get CData Connect AI
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Redash, try CData Connect AI today!