cli | A command line tool to interact with the services

login This command will login and update the state stored on disk with the user_id and login_token It will ask for the username and passwordlist-user This command will list all the registered users in the systemcreate-user This will ask you the information to create a new user It will ask for username, email, and passworddelete-user This command will remove a user from the system BE CAREFUL: This command won't ask for confirmation, nor do any extensive checks, it blindly executes your command It requires to be equal to the username you want to delete Example: delete-user=usernameuser-info This command will show the user info TODO: This command should not show tokens that you do not own, even to admin userslist-package-group This will list all the registered package groupscreate-package-group This will create a new package group It requires to be equal to the package group you want to create Example: create-package-group=namedelete-package-group This will delete a package group BE CAREFUL: This command won't ask for confirmation, nor do any extensive checks, it blindly executes your command It requires to be equal to the package group you want to delete Example: delete-package-group=nameadd-access-token This will add an external systems access token It's up to the repositories how to use them, this is just a storage mechanism, in a generic fashion The access tokens are automatically returned as part of the user object It accepts the following parameters: type, token Example: add-access-token --type=github --token=xxxxxxxxlist-access-token This will list the access tokens for a particular userremove-access-token This will delete an access token from the system BE CAREFUL: This command won't ask for confirmation, nor do any extensive checks, it blindly executes your command It will present you with a list of tokens to deletepublish This will publish a new package through one of the supported/configured repository services You need to provide the type, which is how the repository service is determined The group is the package group you want to publish into The functionality is limited, but you can say the url of the VCS repository to publish from You can override the scanning mechanism that maybe the repository service uses, but this information might not be useful to the repository service, it's only provided as part of the payload and if it's useful then it's available Example: publish --repo=php --group=public --url=https://github.com/reporangler/lib-reporangler NOTE: It is a nice coincidence that publishing an existing package, will also update any existing packages which match the same informationlist-repository This will list all the supported repositoriescreate-repository This will create a repository It requires to be equal to the name of the repository to delete Example: create-repository=npmupdate-repository This will update an existing repository It requires to be equal to the name of the repository to delete It should have a parameter called --name which will be what the repository name will become Example: update-repository=npm --name=rogerdelete-repository This will delete an existing repository It requires to be equal to the name of the repository to delete Example: delete-repository=npmRemove published package Obviously to unpublish something Not entirely sure what combination of fields I need for this yetAssign user repository admin To delegate authority for administrating access to a repository to a team leaderRemove user repository admin To remove the authorityAssign user repository access To allow a user to access package groups with this repositoryRemove user repository access To remove the access to package groups with this repositoryAssign user into repository/package group To grant access to a package group, with a specific repositoryRemove user from repository/package group To remove the access to a package group, within a specific repository