-
Notifications
You must be signed in to change notification settings - Fork 462
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 support for creating and revoking personal access tokens and fetching health check tokens. #336
Comments
This functionality has been released in 4.10.8 |
Thank you @gmessner for implementing this functionality. |
I would like add a suggestion. If we can add static variable inside the AccessTokenUtils class so that the scope names can be clear. Avoids confusion for user. For example, public static final String API = "api";
public static final String READ_USER = "read_user";
public static final String READ_REPOSITORY = "read_repository";
... I feel it could help users understand which variables to supply rather than checking them on GitLab Server. If you want to do this let me know, I will send PR. If you have a better suggestion also let me know. @gmessner |
@baymac |
@gmessner yes, I found enum defined inside |
@baymac |
@gmessner I used it as List<String> GL_PLUGIN_REQUIRED_SCOPE = ImmutableList.of(
Constants.ApplicationScope.API.toValue(), // api
Constants.ApplicationScope.READ_USER.toValue() // read_user
); And it works like that. Btw what is the actual purpose of |
@baymac |
Got it. Thanks. @gmessner |
@baymac Just a heads up, the |
Awesome. :) |
The GitLab API does not support the creation or revocation of personal access tokens, this makes it difficult to automate the testing of GitLab4J-API without a pre-configured and data seeded GitLab server running.
Adding the ability to create and revoke personal access tokens and fetch health check tokens will allow for the full automation of GitLab4J-API using the gitlab-ce docker image.
The text was updated successfully, but these errors were encountered: