To better serve Wise business and customer needs, the PipelineWise codebase needs to shrink. We have made the difficult decision that, going forward many components of PipelineWise will be removed or incorporated in the main repo. The last version before this decision is v0.64.1
We thank all in the open-source community, that over the past 6 years, have helped to make PipelineWise a robust product for heterogeneous replication of many many Terabytes, daily
Singer tap that produces JSON-formatted data from the GitHub API following the Singer spec.
This is a PipelineWise compatible tap connector.
This tap:
- Pulls raw data from the GitHub REST API
- Extracts the following resources from GitHub for a single repository:
- Outputs the schema for each resource
- Incrementally pulls data based on the input state
-
Install
We recommend using a virtualenv:
python3 -m venv venv . venv/bin/activate pip install --upgrade pip pip install .
-
Create a GitHub access token
Login to your GitHub account, go to the Personal Access Tokens settings page, and generate a new token with at least the
repo
scope. Save this access token, you'll need it for the next step. -
Create the config file
Create a JSON file containing the required fields and/or the optional ones. You can decide between allow-list or deny-list strategy combining organization with repos_include and repos_exclude using wildcards.
Config | Required? | Description |
---|---|---|
access_token | yes | The access token to access github api |
start_date | yes | The date inclusive to start extracting the data |
organization | no | The organization you want to extract the data from |
repos_include | no | Allow list strategy to extract selected repos data from organization. Supports wildcard matching |
repos_exclude | no | Deny list to extract all repos from organization except the ones listed. Supports wildcard matching |
include_archived | no | true/false to include archived repos. Default false |
include_disabled | no | true/false to include disabled repos. Default false |
repository | no | (DEPRECATED) Allow list strategy to extract selected repos data from organization(has priority over repos_exclude) |
max_rate_limit_wait_seconds | no | Max time to wait if you hit the github api limit. DEFAULT to 600s |
Example:
{
"access_token": "ghp_16C7e42F292c6912E7710c838347Ae178B4a",
"organization": "singer-io",
"repos_exclude": "*tests* api-docs",
"repos_include": "tap* getting-started pipelinewise-github",
"start_date": "2021-01-01T00:00:00Z",
"include_archived": false,
"include_disabled": false,
"max_rate_limit_wait_seconds": 800
}
You can also pass
singer-io/tap-github another-org/tap-octopus
onrepos_include
.
For retro compatibility you can pass
repository: "singer-io/tap-github singer-io/getting-started"
⚠️ If you have very small repos with total size less than 0.5KB: These will currently be excluded, as the Github repositories API returnssize: 0
for these, andtap_github/__init__.py
currently usessize <= 0
as a way to filter out repos with no commits.
-
Run the tap in discovery mode to get properties.json file
tap-github --config config.json --discover > properties.json
-
In the properties.json file, select the streams to sync
Each stream in the properties.json file has a "schema" entry. To select a stream to sync, add
"selected": true
to that stream's "schema" entry. For example, to sync the pull_requests stream:... "tap_stream_id": "pull_requests", "schema": { "selected": true, "properties": { "updated_at": { "format": "date-time", "type": [ "null", "string" ] } ...
-
Run the application
tap-github
can be run with:tap-github --config config.json --properties properties.json
- Install python test dependencies in a virtual env and run nose unit and integration tests
python3 -m venv venv
. venv/bin/activate
pip install --upgrade pip
pip install -e .[test]
- To run unit tests:
pytest tests/unittests