-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Ship API v3 #6169
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
Ship API v3 #6169
Conversation
* Remove message about contacting support to get early API v3 access * Remove all mentions to API v3 beta in the docs * Mark API v2 as deprecated * Add a note about where to get the access Token
I gave this PR a short try and there was no way for users to create or revoke access tokens. That was fine for beta but I think for general use users need to be able to create and revoke them. If users can create their own access tokens, we don't need to create them for users and we can probably remove the signal too. |
@davidfischer makes sense. I will make the changes to allow Create/Delete from the profile settings. Thanks! |
98a5451
to
6d8b6cd
Compare
@davidfischer I updated the PR with the ability to Generate/Revoke API Tokens under the profile page. Currently, it allows the user to have only one Token max. Let me know if you think this is the path to go forward. Eventually, when we implement scope-based tokens, we will allow the user to manage more than one token at the same time. |
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
We may decide what to return in I'm blocking this for now so we can think about the proper approach first. |
Co-Authored-By: Santos Gallegos <[email protected]>
Before shipping it, I'd like to do a second pass review to all the code (we may want to remove some non-useful filters, for example) and documentation (maybe a refactor or cleaning). |
Just mention relevant fields (not obvious ones) and status codes.
Removing "Status: blocked" label and calling for a last review of @readthedocs/core team before merging. I'd like to have this deployed in the next deploy hopefully. |
@humitos we should resolve what to do around privacy levels first |
The docs for redirects don't mention what kind of redirects can be created, and also, not all redirects require a |
Some fields are not used. I'm brining some changes from readthedocs#6169 to avoid merge conflicts.
…humitos/ship-api-v3
…humitos/ship-api-v3
…ocs.org into humitos/apiv3-remove-privacy-level
Remove privacy_level field from APIv3
- 405 when authenticated performing a GET. - 302 when un-athenticated performing a GET.
Blocked on #6275 for now. We should merge that one first. |
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.
Some examples from the docs are still showing privacy_level
in the response.
Co-Authored-By: Santos Gallegos <[email protected]>
Can you point me to them? I'm not finding anyone. |
It was removed by mistake. Probably while solving a merge conflict
…humitos/ship-api-v3
…ocs.org into humitos/ship-api-v3
Can't see them anymore, guess merging master was missing? |
Looks like the failing tests are not related to the esling thing, btw |
Creates a Token each time a new User is createdBefore merging this PR (or deploy it), we need to run a Python command to create a Token per User.