Loading GitHub Data to Azure Cosmos DB Using dlt
in Python
We will be using the dlt PostgreSQL destination to connect to Azure Cosmos DB. You can get the connection string for your Azure Cosmos DB database as described in the Azure Cosmos DB Docs.
Join our Slack community or book a call with our support engineer Violetta.
This page provides technical documentation for loading data from GitHub
to Azure Cosmos DB
using the open-source Python library dlt
. You can use this verified source to load data on issues, pull requests, or events from any GitHub
repository onto a destination of your choice by leveraging the GitHub API
. Azure Cosmos DB
is a fully managed NoSQL and relational database designed for modern app development. Start building applications with a free trial. For further information on the GitHub
source, visit GitHub Documentation.
dlt
Key Features
- Easy to get started:
dlt
is a Python library that is easy to use and understand. It is designed to be simple to use and easy to understand. Typepip install dlt
and you are ready to go. - Fetching data from the GitHub API: Learn how to load data from the GitHub API into your desired destination. Learn more
- Managing data loading behaviors: Understand how to append or replace your data during the loading process. Learn more
- Incremental loading and deduplication: Load only new data incrementally and deduplicate existing data to keep your datasets up-to-date. Learn more
- Dynamic data fetching and reducing redundancy: Make your data fetch more dynamic and reduce code redundancy. Learn more
- Securely handling secrets: Learn best practices for securely handling secrets within your data pipeline. Learn more
Getting started with your pipeline locally
0. Prerequisites
dlt
requires Python 3.8 or higher. Additionally, you need to have the pip
package manager installed, and we recommend using a virtual environment to manage your dependencies. You can learn more about preparing your computer for dlt in our installation reference.
1. Install dlt
First you need to install the dlt
library with the correct extras for Azure Cosmos DB
:
pip install "dlt[postgres]"
The dlt
cli has a useful command to get you started with any combination of source and destination. For this example, we want to load data from GitHub
to Azure Cosmos DB
. You can run the following commands to create a starting point for loading data from GitHub
to Azure Cosmos DB
:
# create a new directory
mkdir github_pipeline
cd github_pipeline
# initialize a new pipeline with your source and destination
dlt init github postgres
# install the required dependencies
pip install -r requirements.txt
The last command will install the required dependencies for your pipeline. The dependencies are listed in the requirements.txt
:
dlt[postgres]>=0.3.25
You now have the following folder structure in your project:
github_pipeline/
├── .dlt/
│ ├── config.toml # configs for your pipeline
│ └── secrets.toml # secrets for your pipeline
├── github/ # folder with source specific files
│ └── ...
├── github_pipeline.py # your main pipeline script
├── requirements.txt # dependencies for your pipeline
└── .gitignore # ignore files for git (not required)
2. Configuring your source and destination credentials
The dlt
cli will have created a .dlt
directory in your project folder. This directory contains a config.toml
file and a secrets.toml
file that you can use to configure your pipeline. The automatically created version of these files look like this:
generated config.toml
# put your configuration values here
[runtime]
log_level="WARNING" # the system log level of dlt
# use the dlthub_telemetry setting to enable/disable anonymous usage data reporting, see https://dlthub.com/docs/telemetry
dlthub_telemetry = true
generated secrets.toml
# put your secret values and credentials here. do not share this file and do not push it to github
[sources.github]
access_token = "access_token" # please set me up!
[destination.postgres]
dataset_name = "dataset_name" # please set me up!
[destination.postgres.credentials]
database = "database" # please set me up!
password = "password" # please set me up!
username = "username" # please set me up!
host = "host" # please set me up!
port = 5432
connect_timeout = 15
2.1. Adjust the generated code to your usecase
3. Running your pipeline for the first time
The dlt
cli has also created a main pipeline script for you at github_pipeline.py
, as well as a folder github
that contains additional python files for your source. These files are your local copies which you can modify to fit your needs. In some cases you may find that you only need to do small changes to your pipelines or add some configurations, in other cases these files can serve as a working starting point for your code, but will need to be adjusted to do what you need them to do.
The main pipeline script will look something like this:
import dlt
from github import github_reactions, github_repo_events, github_stargazers
def load_duckdb_repo_reactions_issues_only() -> None:
"""Loads issues, their comments and reactions for duckdb"""
pipeline = dlt.pipeline(
"github_reactions",
destination='postgres',
dataset_name="duckdb_issues",
full_refresh=True,
)
# get only 100 items (for issues and pull request)
data = github_reactions(
"duckdb", "duckdb", items_per_page=100, max_items=100
).with_resources("issues")
print(pipeline.run(data))
def load_airflow_events() -> None:
"""Loads airflow events. Shows incremental loading. Forces anonymous access token"""
pipeline = dlt.pipeline(
"github_events", destination='postgres', dataset_name="airflow_events"
)
data = github_repo_events("apache", "airflow", access_token="")
print(pipeline.run(data))
# if you uncomment this, it does not load the same events again
# data = github_repo_events("apache", "airflow", access_token="")
# print(pipeline.run(data))
def load_dlthub_dlt_all_data() -> None:
"""Loads all issues, pull requests and comments for dlthub dlt repo"""
pipeline = dlt.pipeline(
"github_reactions",
destination='postgres',
dataset_name="dlthub_reactions",
full_refresh=True,
)
data = github_reactions("dlt-hub", "dlt")
print(pipeline.run(data))
def load_dlthub_dlt_stargazers() -> None:
"""Loads all stargazers for dlthub dlt repo"""
pipeline = dlt.pipeline(
"github_staragarzers",
destination='postgres',
dataset_name="dlthub_staragarzers",
full_refresh=True,
)
data = github_stargazers("dlt-hub", "dlt")
print(pipeline.run(data))
if __name__ == "__main__":
load_duckdb_repo_reactions_issues_only()
load_airflow_events()
load_dlthub_dlt_all_data()
load_dlthub_dlt_stargazers()
Provided you have set up your credentials, you can run your pipeline like a regular python script with the following command:
python github_pipeline.py
4. Inspecting your load result
You can now inspect the state of your pipeline with the dlt
cli:
dlt pipeline github_events info
You can also use streamlit to inspect the contents of your Azure Cosmos DB
destination for this:
# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline github_events show
5. Next steps to get your pipeline running in production
One of the beauties of dlt
is, that we are just a plain Python library, so you can run your pipeline in any environment that supports Python >= 3.8. We have a couple of helpers and guides in our docs to get you there:
The Deploy section will show you how to deploy your pipeline to
- Deploy with GitHub Actions: Learn how to set up and deploy your
dlt
pipeline using GitHub Actions for automated CI/CD. Check out the guide here. - Deploy with Airflow and Google Composer: Follow this guide to deploy your
dlt
pipeline using Airflow, a powerful workflow management tool, and Google Composer. Read more here. - Deploy with Google Cloud Functions: Discover how to deploy your
dlt
pipeline using Google Cloud Functions for serverless execution. Find the instructions here. - Explore other deployment options: Browse through various other methods and detailed guides to deploy your
dlt
pipeline. Explore more here.
The running in production section will teach you about:
- How to Monitor your pipeline: Learn how to effectively monitor your
dlt
pipeline in production to ensure it runs smoothly. How to Monitor your pipeline - Set up alerts: Set up alerts to get notified about any issues or important events in your
dlt
pipeline. Set up alerts - And set up tracing: Implement tracing to track the execution of your
dlt
pipeline and diagnose problems. And set up tracing
Available Sources and Resources
For this verified source the following sources and resources are available
Source github_repo_events
"GitHub repo events source provides data about activities and interactions within a repository."
Resource Name | Write Disposition | Description |
---|---|---|
repo_events | append | Retrieves all the repository events associated with the GitHub repository. This includes information about the actor (user who triggered the event), organization, payload (specific details about the event), and the repository itself. |
Additional pipeline guides
- Load data from Salesforce to Supabase in python with dlt
- Load data from Cisco Meraki to Redshift in python with dlt
- Load data from Spotify to DuckDB in python with dlt
- Load data from Salesforce to MotherDuck in python with dlt
- Load data from Vimeo to AWS Athena in python with dlt
- Load data from Slack to DuckDB in python with dlt
- Load data from Attio to YugabyteDB in python with dlt
- Load data from IBM Db2 to Snowflake in python with dlt
- Load data from Vimeo to Timescale in python with dlt
- Load data from Jira to The Local Filesystem in python with dlt