Create a custom configured resource for Strava API #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently, the Strava API configuration is hard-coded and baked into the
assets/activities.py
as a function. This works if you are only developing a single pipeline for testing, but does not scale since the configured API is not modular and/or reusable.This PR aims to create a reusable resource for the Strava API that can be used as a Dagster resource just like the dbt or duckdb resources.
Details
Utilized the
ConfigurableResource
class to be inherited by a newStravaAPIResource
class in order to import and reuse the API across my project and to follow best practices. This object is in theresources/
directory and is used just like any other Dagster resource and inherits the same benefits.