To have features like vulnerability management (and many others), we need to have some kind of authentication in huskyCI.
If we have a CLI command that will log in users using Github and Gitlab, for instance, we will have the possibility to check which repositories a developer has access to, profile image, and many others.
It would be great if
We have an OAuth2 solution coded in our CLI by implementing a cobra command login.
What we expect
By typing the following command, huskyCI must be able to redirect the authorization request to an OAuth2 provider (Github? ❤️) open a web browser for the user to complete the login, and store the token into a file .huskyci to be used later on.
I would like to take it up! I think to use the device flow for the authorization and I need to know the client id (for the first time I can create my own GitHub App).
Motivation
To have features like vulnerability management (and many others), we need to have some kind of authentication in huskyCI.
If we have a CLI command that will log in users using Github and Gitlab, for instance, we will have the possibility to check which repositories a developer has access to, profile image, and many others.
It would be great if
We have an OAuth2 solution coded in our CLI by implementing a cobra command
login
.What we expect
By typing the following command, huskyCI must be able to redirect the authorization request to an OAuth2 provider (Github? ❤️) open a web browser for the user to complete the login, and store the token into a file
.huskyci
to be used later on.Tips