You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some kci user commands such as kci user password reset and kci user verify currently take a username argument to find the user in order to be consistent with other commands. However, these operations rely on an email address and could also be done just by providing an email address instead of the username. Generally speaking, as usernames can't contain symbols such as @ (to be confirmed...) then users can be found using either their username or email in exactly the same way.
So all the kci user command that have a username argument could instead have a login argument which could be either a username or an email address. Then we could have a helper method in kernelci.cli to get a user from the API:
Some
kci user
commands such askci user password reset
andkci user verify
currently take a username argument to find the user in order to be consistent with other commands. However, these operations rely on an email address and could also be done just by providing an email address instead of the username. Generally speaking, as usernames can't contain symbols such as@
(to be confirmed...) then users can be found using either their username or email in exactly the same way.So all the
kci user
command that have ausername
argument could instead have alogin
argument which could be either a username or an email address. Then we could have a helper method inkernelci.cli
to get a user from the API:This might even be made part of the APIHelper class, without the Click exception.
The text was updated successfully, but these errors were encountered: