-
Notifications
You must be signed in to change notification settings - Fork 989
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
clarify gitlab token refresh behavior #6839
Conversation
this pr clarifies gitlab token refresh behavior Resolves #6830
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
simplify and add faq
|
||
If you're receiving a "Refresh token" message, don't worry — dbt Cloud automatically refreshes this project access token for you, which means you never have to manually rotate it. | ||
|
||
If you still experience any token refresh errors, please try disconnecting and reconnecting the repository in dbt Cloud to refresh the token. |
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.
Hiya @mirnawong1
This is a non-blocking suggestion. Would it be worthwhile linking users to this page: https://docs.getdbt.com/faqs/Troubleshooting/gitlab-authentication#1st-workaround for info on disconnecting and reconnecting their repo?
Kind Regards
Natalie
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 this is a step for deploy keys so not sure if it works! but i can clarify to disconnect the repo in their project
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.
Hiya @mirnawong1
Thanks for creating this PR. I've left two non-blocking suggestions and approved this for you.
Kind Regards
Natalie
Co-authored-by: nataliefiann <[email protected]>
Feedback from company around our native Gitlab integration. They ran into some confusion with getting notified about a project token expiring (which dbt Cloud automatically refreshes) and manually rotated the token which caused their CI pipelines to no longer receive pass/fail status in Gitlab from dbt Cloud.
this pr clarifies gitlab token refresh behavior
Resolves #6830
source: https://dbtcloud.zendesk.com/agent/tickets/81923
🚀 Deployment available! Here are the direct links to the updated files: