I have three question regarding the mender-cli.
- Is it possible to login to the server e.g. https://hosted.mender.io or self hosted in Enterprise with the tenant token instead of username and password? I don’t like the idea of having a plain text file lying around with my credentials.
- Currently i linked my github account to mender.io, but the login does not work. I created the ~/.mender-clirc json file
"server" : "https://hosted.mender.io"
When i try to login i get 401
$ mender-cli login
Using configuration file: /home/armin/.mender-clirc
FAILURE: login failed with status 401
Therefore i cannot use the mender-cli for artifacts managing within my CI/CD.
- Why are issues in the github-repo for mender-cli disabled? I would create an issue as it is the github way to go.
Right now we only support user/password login. There is something in the works to support “API keys” functionality.
Many CI environments have the possibility to manage secrets, to avoid storing them as plain text files. I do not know if that is a possibility for you.
Currently i linked my github account to mender.io, but the login does not work. I created the ~/.mender-clirc json file
Will defer to @tranchitella or @peter.
Why are issues in the github-repo for mender-cli disabled? I would create an issue as it is the github way to go.
Issues on github are disabled for all of our repositories, mostly I think since we have many repositories (59 and counting) and we prefer to centrally manage any questions/issues.
The prefererad is https://hub.mender.io or https://tracker.mender.io/projects/MEN (also public)
thanks for clearing things up.
I created a PR (https://github.com/mendersoftware/mender-cli/pull/76) that makes configuration file handling and password handling a little bit better. The current behavior was a little non verbose. Also the interactive password prompt never got used.
were you able to login with github?