This documentation is for an older version (1.4.7) of Dagster. You can view the version of this page from our latest release below.
This library provides an integration with GitHub Apps, to support performing various automation operations within your github repositories and with the tighter permissions scopes that github apps allow for vs using a personal token.
Presently, it provides a thin wrapper on the github v4 graphql API.
To use this integration, you’ll first need to create a GitHub App for it.
Create App: Follow the instructions in
https://developer.github.com/apps/quickstart-guides/setting-up-your-development-environment/, You will end up with a private key and App ID, which will be used when configuring the
dagster-github
resource. Note you will need to grant your app the relevent permissions
for the API requests you want to make, for example to post issues it will need read/write access
for the issues repository permission, more info on GitHub application permissions can be found
here
Install App: Follow the instructions in https://developer.github.com/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account
Find your installation_id: You can pull this from the GitHub app administration page,
https://github.com/apps/<app-name>/installations/<installation_id>
. Note if your app is
installed more than once you can also programatically retrieve these IDs.
Sharing your App ID and Installation ID is fine, but make sure that the Private Key for your app is stored securily.
Now, you can create issues in GitHub from Dagster with the GitHub resource:
import os
from dagster import job, op
from dagster_github import github_resource
@op(resource_defs={'github'})
def github_op(context):
context.resources.github.create_issue(
repo_name='dagster',
repo_owner='dagster-io',
title='Dagster\'s first github issue',
body='this open source thing seems like a pretty good idea',
)
@job(resource_defs={'github': github_resource})
def github_job():
github_op()
github_job.execute_in_process(
run_config={'resources': {'github': {'config': {
"github_app_id": os.getenv('GITHUB_APP_ID'),
"github_app_private_rsa_key": os.getenv('GITHUB_PRIVATE_KEY'),
"github_installation_id": os.getenv('GITHUB_INSTALLATION_ID'),
}}}}
)
Run the above code, and you’ll see the issue appear in GitHub:
GitHub enterprise users can provide their hostname in the run config. Provide github_hostname
as part of your github config like below.
github_job.execute_in_process(
run_config={'resources': {'github': {'config': {
"github_app_id": os.getenv('GITHUB_APP_ID'),
"github_app_private_rsa_key": os.getenv('GITHUB_PRIVATE_KEY'),
"github_installation_id": os.getenv('GITHUB_INSTALLATION_ID'),
"github_hostname": os.getenv('GITHUB_HOSTNAME'),
}}}}
By provisioning github_resource
as a Dagster job resource, you can post to GitHub from
within any op execution.
import os
from dagster import job, op
from dagster_github import github_resource
@op(resource_defs={'github'})
def github_op(context):
context.resources.github.execute(
query="""
query get_repo_id($repo_name: String!, $repo_owner: String!) {
repository(name: $repo_name, owner: $repo_owner) {
id
}
}
""",
variables={"repo_name": repo_name, "repo_owner": repo_owner},
)
@job(resource_defs={'github': github_resource})
def github_job():
github_op()
github_job.execute_in_process(
run_config={'resources': {'github': {'config': {
"github_app_id": os.getenv('GITHUB_APP_ID'),
"github_app_private_rsa_key": os.getenv('GITHUB_PRIVATE_KEY'),
"github_installation_id": os.getenv('GITHUB_INSTALLATION_ID'),
}}}}
)
Github Application ID, for more info see https://developer.github.com/apps/
Github Application Private RSA key text, for more info see https://developer.github.com/apps/
Github Application Installation ID, for more info see https://developer.github.com/apps/
Github hostname. Defaults to api.github.com, for more info see https://developer.github.com/apps/