GitHub
Source Connector
Overview
This source connector fetches from the GitHub REST API.
Streams
Data Source | Stream Name |
---|---|
organization audit log | organization_auditlog |
Prerequisites
Authentication
The following authentication options are supported by this connector:
Authentication Method | Supported | Documentation |
---|---|---|
Personal access token(s) | yes | Managing your personal access tokens |
GitHub App authentication | yes | GitHub App installation |
Personal access token(s)
Multiple personal access tokens can be used to load balance your API consumption.
Instructions
- Create a Personal access token (classic)
- Expiration: No expiration
- Scopes:
read:audit_log
Personal access token Configuration Fields
Field | Required | Description |
---|---|---|
Personal access token(s) | yes | Comma separated list of personal access tokens. Multiple tokens can be used to load balance your API quota consumption. |
Github App authentication
- Register a GitHub App for your organization.
- Homepage URL
- Webhook
- Deselect the Active checkbox
- Permissions
- Organization permissions:
Read-only
- All other permissions should be set to
No access
- Organization permissions:
- Once created, copy the Client ID to be used in the Tarsal configuration later.
- Generate a private key
- Under the General sub navigation for the App, click the Generate private key button. This will download a certificate file named something like
app-name-date.private-key.pem
. Save this file as it will be used in the Tarsal configuration later.
- Under the General sub navigation for the App, click the Generate private key button. This will download a certificate file named something like
- Install the App
- Back at the top in the left navigation, click Install App and then click the Install button
- After clicking install you will be navigated to a website with a link that looks like this:
https://github.com/settings/installations/{installation_id}
Copy theinstallation_id
from the path in the URL to be used in the Tarsal Configuration later- You can find the
installation_id
later by navigation to Profile > Settings > Integrations > Applications and clicking Configure on the App
- You can find the
GitHub App Configuration Fields
Field | Required | Description |
---|---|---|
Client ID | yes | The GitHub App Client ID |
Installation ID | yes | The ID corresponding to the specific installation of your application. Different from the client ID from and can be found in the URL of the app installation. |
Private Key | yes | The GitHub App private key. Found in the *.private-key.pem file downloaded during the app creation process. |
Configuration
Field | Required | Description | Example |
---|---|---|---|
Organization/Repositories | yes | Space separated list of organization/repository .Examples: All repositories: tarsalhq/* Single repository: tarsalhq/repo1 Multiple repositories: tarsalhq/repo1 tarsalhq/repo2 | tarsalhq/* |
Authentication | yes | Choose one of the two methods listed in the authentication section above |
Connector Limitations
- The source IP address for events, used to populate the tarsal normalized field
t_ip_address
, is only available to enterprise customers.
Updated 11 days ago