kamu-cli
kamu-cli copied to clipboard
`kamu login`: revisit command ergonomics
At the moment, from a UX perspective, we can perform a login in three ways:
-
kamu login password $USER $PASSWORD $KAMU_NODE_URL
- ✅ Password authorization (calls kamu node API)
-
kamu login oauth github $TOKEN $KAMU_NODE_URL
- ✅ OAuth token authorization (calls kamu node API)
-
kamu login --access-token $TOKEN $KAMU_NODE_URL
- :warning: Only saves the received token to a file (
.kamu/.kamutokenstore) without API calls
As a suggestion: make kamu login --access-token an alias for kamu login oauth github.
This way we will have a single code path to work with the token and the command kamu login (3).) will not be misleading.