-
Notifications
You must be signed in to change notification settings - Fork 976
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
Deprecating user API key from docs #6358
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Looks great Matt! Just some small suggestions on acronym vs spelling it out and some wording suggestions.
|
||
::: | ||
It's recommended that you rotate your PATs at regular intervals for security purposes. To rotate your PATs, create a new token and, once it's in place, delete the old 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.
It's recommended that you rotate your PATs at regular intervals for security purposes. To rotate your PATs, create a new token and, once it's in place, delete the old token. | |
It's recommended that you regularly rotate your PATs to maintain robust security. To rotate your PATs, create a new token and, once it's in place, delete the old token. |
|
||
:::info New | ||
Copy the token prior to closing the window. _It will not be available after and you will have to create a new token if you lose it._ |
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.
Can this be step #4?
|
||
Each dbt Cloud user with a [Developer license](https://docs.getdbt.com/docs/cloud/manage-access/seats-and-users) can create a new personal access token (PAT) to access the dbt Cloud API and dbt Cloud CLI. This token can execute queries against the dbt Cloud API on the user's behalf. To access dbt Cloud APIs and resources on behalf of the _account_, we recommend using service Tokens instead. Learn more about [which token type you should use](/docs/dbt-cloud-apis/authentication#which-token-type-should-you-use) to understand the token differences. | ||
To delete a 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.
This might be easier for folks to find if we elevate it to an L2. Whatever you decide for creating a PAT, you should do here identifying the acronym in the header or 1st paragraph.
To delete a token: | |
## Delete a personal access token (PAT) | |
If you're rotating your tokens, make sure to create a new token before deleting the old one. | |
To delete a PAT: |
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.
We define (PAT) in the headers above, it might be a little overkill here. Makes the link simpler to leave it off
Co-authored-by: Leona B. Campbell <[email protected]>
Co-authored-by: Leona B. Campbell <[email protected]>
Co-authored-by: Leona B. Campbell <[email protected]>
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.
Looks good!
What are you changing in this pull request and why?
User API keys have been deprecated. Removing implementation instructions and references in the docs. Replacing with Account-scoped PATs.
Checklist
🚀 Deployment available! Here are the direct links to the updated files: