-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add local dev and update docs for Sling #75
Conversation
Your pull request is automatically being deployed to Dagster Cloud.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm thanks for getting this all sorted
- you will also need to install the packages in the "sling" extra (e.g. `pip install -e ".[dev,sling]")`) | ||
- You'll need to obtain the credentials for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY | ||
- then run `dagster dev` and both `hooli_demo_assets` and `hooli_data_eng` code locations will load | ||
- NOTE: if you are running Sling locally, there is currently an error message if you already have a duckdb database set up the first time you run the Sling integration. You'll need to delete it and have the `location` asset be the the first thing you materialize. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not to hold up this PR, but did you happen to create a bug for this? I vaguely remember running into it way back when.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean on Sling's repo or here for us? Either way I didn't but can do
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should raise it internally and then we can decide if it should go back to Sling too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done #79
the Sling loader was failing in prod, and I wanted to debug it. There must have been an update to Sling between version upgrades because we needed to change the AWS_BUCKET from
s3://{bucket_name}/{folder_path}
(old) to just{bucket_name}
. That was an env var change which is now live, but for me to figure that out I had to get the local version working. This PR adds that local support:setup.py
to includedagster-embedded-elt