-
Notifications
You must be signed in to change notification settings - Fork 14
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
MVP of dbt-based data publishing framework #1505
Conversation
1 similar comment
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.
- thank you for writing all these docs, I know it is not your favorite 🙏
- this is cool and I am excited!
- mostly nit picky comments, I just want the docs to be as detailed as possible in case this sits for a bit and then we have to come back to it later..... I think my implicit standard is -- could someone who's not Andrew and can't talk to Andrew successfully publish based on the documentation here alone? (if you don't think that level is possible yet, I guess perhaps that will need to wait)
- ETA: can you update description? seems like linked Google doc is obsolete, so can probably remove. and info on any testing would be good. also -- I don't think this PR does close all those tickets? we still need to actually implement, right? this gives the framework / infra to publish but does not actually publish
Another request per meeting with Eric: can we update to give an option (maybe a modification of |
done! the bucket is a CLI option still, but there's separate dry-run and deploy concepts now. |
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.
ok just one q
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.
ok sorry, just wondering if we can update docs based on the changing defaults
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.
yay 🎉
Description
This PR implements a minimum-viable data publishing framework based on dbt exposures. Initially, our goal is to primarily support uploads to CKAN; that process is documented in this PR as well.
Once deployed, #284 and #427 can be closed
Type of change
How has this been tested?
I've tested metadata generation and GCS writing locally. However, we can't test publishing to CKAN until we actually go through the process, which we will be doing once this PR is merged.
Screenshots (optional)