-
Notifications
You must be signed in to change notification settings - Fork 137
[Do Not Merge] Add API Documentation for Multi-Team Tokens #875
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
base: main
Are you sure you want to change the base?
[Do Not Merge] Add API Documentation for Multi-Team Tokens #875
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
101ca21
to
a89b19a
Compare
1dcb277
to
04b3595
Compare
04b3595
to
3aa2f3b
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.
A few suggestions.
18dbeba
to
190eb3e
Compare
190eb3e
to
919ae1a
Compare
919ae1a
to
2b46fe6
Compare
Hi, @robin-norwood! I'm seeing a "Vercel Preview Comments" failure on this PR, but I cannot see the actual failure due to a lack of access to Vercel -- do you have any pointers on how should I go about resolving the issue? |
I resolved the comment! It was about a header, and I checked and your already fixed it! |
Thank you so much for doing that, @rkoron007! I appreciate your help 🙌 |
69f51e9
to
0aeb1c7
Compare
|
||
| Key path | Type | Default | Description | | ||
| ----------------------------- | ------ | ------- | --------------------------------------------------------------------------------------------------------------- | | ||
| `data.type` | string | | Must be `"authentication-tokens"`. | |
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.
Updated this to be the plural authentication-tokens
per this Slack comment!
```json | ||
{ | ||
"data": { | ||
"type": "authentication-tokens", |
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.
Updated this to be the plural authentication-tokens
per this Slack comment!
ff3537e
to
17eb6d4
Compare
17eb6d4
to
f3a6bf9
Compare
Hi, @robin-norwood 👋 This PR is ready for re-review whenever you have a moment, please and thank you so much! |
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!
What
Update the Team Token API documentation to reflect the changes to team tokens, which include allowing multiple team tokens to be generated for a team and flagging the existing Team Token API as "legacy."
Why
These updates are relevant to the work being done for the allowance of multiple team tokens. The work being done adds a new API endpoint for creating multiple team tokens and now requires that Team Tokens (using the new API) set a description for the token, similar to the user experience when creating User Tokens. The existing Team Token API that only allows a single team token to be created will still exist so that users leveraging that API do not have to worry about data loss, however, this API is considered to be "legacy" now. Additionally, the work being done includes changes to the regenerate token button in the UI--this button will cease to exist once the changes are rolled out. The API documentation does not mention this button much, so very small wording tweaks were made to reflect this. Here's a link to the RFC for more information regarding the updates, and the Jira ticket for the work.
Merge Checklist
If items do not apply to your changes, add (N/A) and mark them as complete.
Pull Request
Content
website/redirects.js
for moved, renamed, or deleted pages.Reviews