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 Google secrets #859
add Google secrets #859
Conversation
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
70bd6c9
to
5948e3f
Compare
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! you could move qdrant to destinations in google secrets (see my comment)
# Slack hook for chess in production example | ||
RUNTIME__SLACK_INCOMING_HOOK: ${{ secrets.RUNTIME__SLACK_INCOMING_HOOK }} | ||
# Mongodb url for nested data example | ||
MONGODB_PIPELINE__SOURCES__CONNECTION_URL: ${{ secrets.MONGODB_PIPELINE__SOURCES__CONNECTION_URL }} | ||
|
||
# Qdrant credentials | ||
DESTINATION__QDRANT__CREDENTIALS__LOCATION: ${{ secrets.DESTINATION__QDRANT__CREDENTIALS__LOCATION }} |
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.
maybe you could add qdrant to destination
secret in google secrets and remove that? optional.
* add Google secrets * test_config_providers doesn't return anything * return test utils * config.toml not from google secrets * set working dir * remove return typing * remove unused line * add google client to deps * delete sources ENVs * return back performance
Description
Enable Google Secrets for doc tests (code-snippets).
Related Issues
Additional Context