dagster_rudderstack
A Dagster library for triggering Reverse ETL syncs and Profiles runs in RudderStack.
Installation
Use pip to install the library.
pip install dagster_rudderstack
Configuration
Setup RudderStack resource with your service access token.
[!NOTE] For production use cases, RudderStack recommends using a service access token instead of personal access token.
# resources.py
from dagster_rudderstack.resources.rudderstack import RudderStackRETLResource
rudderstack_retl_resource = RudderStackRETLResource(
access_token="access_token")
RudderStackRETLResource exposes other configurable parameters as well. Mostly default values for them would be recommended.
- rs_cloud_url: RudderStack cloud endpoint.
- request_max_retries: The maximum number of times requests to the RudderStack API should be retried before failng.
- request_retry_delay: Time (in seconds) to wait between each request retry.
- request_timeout: Time (in seconds) after which the requests to RudderStack are declared timed out.
- poll_interval: Time (in seconds) for polling status of triggered job.
- poll_timeout: Time (in seconds) after which the polling for a triggered job is declared timed out.
Similarly if need to define ops and jobs for Profiles, can define a resource for profiles.
# resources.py
from dagster_rudderstack.resources.rudderstack import RudderStackProfilesResource
rudderstack_profiles_resource = RudderStackProfilesResource(
access_token="access_token")
Ops and Jobs
Define ops and jobs with schedule. Provide the connection id for the sync job
# jobs.py
from dagster import job, ScheduleDefinition, ScheduleDefinition
from dagster_rudderstack.ops.retl import rudderstack_sync_op, RudderStackRETLOpConfig
from .resources import rudderstack_retl_resource
@job(
resource_defs={
"retl_resource": rudderstack_retl_resource
}
)
def rs_retl_sync_job():
rudderstack_sync_op()
rudderstack_sync_schedule = ScheduleDefinition(
job=rs_retl_sync_job,
cron_schedule="* * * * *", # Runs every minute
run_config={"ops": {"rudderstack_sync_op": RudderStackRETLOpConfig(connection_id="connection_id")}},
default_status=DefaultScheduleStatus.RUNNING
)
Similarly one can define ops for profiles job. Provide the profiles id for the profiles project to run.
from dagster_rudderstack.ops.profiles import rudderstack_profiles_op, RudderStackProfilesOpConfig
from .resources import rudderstack_profiles_resource
@job(
resource_defs={
"profiles_resource": rudderstack_profiles_resource
}
)
def rs_profiles_job():
rudderstack_profiles_op()
RudderStackProfilesOpConfig also supports passing extra parameters that can be used for profile run via profiles API
In case, one wants to define a job as sequence of ops e.g, a profile run and then reverse etl sync run. Note that, if one of the op fails, job will raise exception without running the next op. One can configure job as needed. For example, can use try/catch exception to ignore op failure and still run second op.
from dagster_rudderstack.ops.retl import rudderstack_sync_op, RudderStackRETLOpConfig
from dagster_rudderstack.ops.profiles import rudderstack_profiles_op, RudderStackProfilesOpConfig
from .resources import rudderstack_retl_resource, rudderstack_profiles_resource
@job(
resource_defs={
"profiles_resource": rudderstack_profiles_resource,
"retl_resource": rudderstack_retl_resource
}
)
def rs_profiles_then_retl_run():
profiles_op = rudderstack_profiles_op()
rudderstack_sync_op(start_after=profiles_op)
rudderstack_sync_schedule = ScheduleDefinition(
job=rs_profiles_then_retl_run,
cron_schedule="0 0 * * *", # Runs day
run_config=RunConfig(
ops={
"rudderstack_profiles_op": RudderStackProfilesOpConfig(profile_id="profile_id", parameters=[<add list of optional parameters>]),
"rudderstack_sync_op": RudderStackRETLOpConfig(connection_id="connection_id"),
}
)
default_status=DefaultScheduleStatus.RUNNING
)
Release files for dagster-rudderstack 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dagster_rudderstack-1.3.0.tar.gz | 16.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dagster_rudderstack-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.2 kB
Release files / dagster_rudderstack-1.3.0.tar.gz
| Download URL | dagster_rudderstack-1.3.0.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f300117c3240e24a46353b27929ce7f3cd33391d2c323f60ac21e64beb9d8a3
|
|
BLAKE2b-256 checksum How to use checksums |
d99266bbd64ef08c97464d1514ce70827a70c737b3523dff88fd02d148559c54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 14, 2025.
Transparency logRelease files / dagster_rudderstack-1.3.0-py3-none-any.whl
| Download URL | dagster_rudderstack-1.3.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bba8aa67e0fda21c7581fa7e8ab704a35593b5a149be93b65d71b4a946b710c3
|
|
BLAKE2b-256 checksum How to use checksums |
178fa91cdade97f9ea41e4698c758755dfe7bcd1931b1114f58ce78ebe7b0b76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 14, 2025.
Transparency log